The University of Tennessee

• Calendars
  • EVENT CALENDAR
  • ACADEMIC CALENDAR
  • ACADEMIC TIMETABLE
  • KEY DATES
• Maps
  • Interactive
  • Archive
• A-Z
  • A-E
  • F-J
  • K-O
  • P-T
  • U-Z
• People
  • CAMPUS DIRECTORY
  • CHANCELLOR
  • PROVOST
  • VICE CHANCELLORS
  • ACADEMIC DEANS
• E-mail
  • TMAIL
  • VOLMAIL
  • LISTSERV
  • ABOUT
• Logins
  • MYUTK
  • ONLINE@UT
  • IRIS
  • WEB ACCOUNTS
  • PASSWORDS
• Libraries
  • UNIVERSITY LIBRARIES
  • AGRICULTURE & VET MED
  • LAW
  • MEDICAL
  • MUSIC
  • SOCIAL WORK
  • SPACE INSTITUTE
  • SPECIAL COLLECTIONS
• COE
  • College of Engineering
  • Advising
  • Diversity
  • Outreach
  • Study Abroad
  • Biosystems
  • Chemical & Biomolecular
  • Civil & Environmental
  • Electrical & Computer Science
  • Industrial & Systems
  • Materials Science
  • Mechanical, Aerospace, Biomedical
  • Nuclear
• EFD
  • Engineering Fundamentals
  • EF 105
  • EF 151
  • EF 152
  • EF 230
  • EF 402

EF 230 Fall, 2013

Computer Solution of Engineering Problems

Main Navigation:

• Announcements
• Instructor/GTAs
• Syllabus
• Calendar
• Section Info
• Procedures

• Labs
• Homeworks
• Projects
• Exams
• In-class Examples
• Drop Box

• Help Sessions
• Discussion Board
• Mathworks web site
• Search m-files
• Example m-files

• Control Panel
• Student Lists
• Grade Entry
• Grade Stats
• Edit page
• Browse
• Logoff

• EF 105
• EF 151
• EF 152
• EF 402

EF 230 Fall, 2013 Feedback

Too late - this form has expired

Please take a few minutes and give us feedback on the class. Your constructive comments are invaluable to us in helping improve the class each semester. You will receive extra credit for completing this form. Thanks.

Labs

Rate the overall quality of the EF 230 class.

11% (23/210) Very good (1) 44% (92/210) Good (2) 31% (65/210) Average (3) 11% (23/210) Marginal (4) 3% (7/210) Poor (5) 0% (0/210) N/A (0) Avg: 2.52, NZAvg: 2.52, sum=529, cnt=210, nzcnt=210

General comments/suggestions about this class.

1.  go matlab 2.  The class is good, but I don't see myself using MATLAB in the future. I would have rather learned how to use HYSYS which is what I need for my major. 4.  Im just not good really with matlab or programming so i felt like no matter how much i studied, or paid attention the best i could do in this class was a b. 5.  The way the class is taught isn't very good, all the TA's do is read whats on the website. They do, however, help whenever asked to. I feel the TA's should help get the material across better. 7.  none 8.  I think the class is organized very well. 10.  Class felt rushed during some of the more complex parts of the class, but overall was set at a fair pace. I enjoyed the projects, and they helped me get a better understanding of the material we were studying. 11.  The projects are entirely too long for a 2 hour class, and/or there are too many. I feel like it's completely absurd to have 8 hour + projects for 2 credits. 13.  good class 14.  I wish that instead of it being a general EF class, it was major specific. This way we could learn the general aspects of MATLAB but at the same time have it geared towards what we will be using it for later in life. 15.  I had to look up almost every homework question. I greatly relied on outside sources to learn the material. Much of the material required in the tests, projects, and homework was not thoroughly covered on the website. The website was disorganized and covered the topics incompletely. I gave up on paying attention to what the TA's were doing during class because the projector was dim, and the text was small. So I learned mostly from the website and MATLAB's help documentation. Luckily I have had previous MATLAB experience, because otherwise the class would have been a complete failure. The TA's did fairly well with what they were given. Showing up to labs was a waste of time. I basically taught myself everything. 16.  Very useful to know for many engineering problems, not very fun though. 17.  It was an interesting class. 18.  Remove participation grade and grade learning alone. 20.  The class as a whole is good, because I feel like I know matlab better. I think the homeworks should always include a coding section for the students to learn better. It is easy to just click through multiple choice after getting frustrated. 21.  It's a two hour class that requires about 10 hours a week of work, including class time, when you average it all out. That's absurd. Also, instead of a large final project AND final exam, why not just do one or the other? 23.  I enjoyed the way 105 was taught with Steve. 24.  Instructors were helpful. Class material wasn't up my ally though and I didn't find it very interesting. 25.  I learned the material rather well, I feel I am proficient at simple matlab coding now. I sometimes felt the multiple choice was sometimes a little useless and didn't improve my knowledge. 26.  Went fast and expected us to fully know matlab when entering 27.  My least favorite class. We learned so many different aspects of matlab in so much detail it was hard to keep up sometimes. The projects were also extremely complex. 31.  Really wish we had a book. TA's are sometimes unclear of the material themselves, and not all required content is explained in depth in the notes. A book would be beneficial. 32.  Put more information about MATLAB on the website. 33.  I enjoyed the class, but the program can be difficult for many people. 34.  Just a hard class. I never really knew how to study for tests. 35.  The TA's did a good job teaching 36.  I learned several new MatLab functions. They will be helpful in my future classes. 37.  The lectures are boring and pointless as we can read what is on the labs. Additionally, projects, such as the last one, that are more independently based help me significantly more than the others. 38.  Especially in the later labs the actual lab pages themselves were pretty sparse by the end. While the beginning of the class was easy and required no notes or anything, by the end if you missed anything in the class it was difficult to go back and rework. Furthermore, some of the example files contained a lot of stuff not necessarily applicable that may make it difficult for some people to sort through for what process they are actually looking for. Also, there were several multiple choice questions across the tests that were very vague and had two possibilities, at least in my reasoning. But of course, only one is correct. Finally, some of the grading on projects seemed arbitrary. For instance, I forgot to put my name on one of the graphs on a program and lost 8 points. Am I to believe that a name on a graph is worth 8% of the entire project? I realize the point is to teach people to pay attention to detail and make sure that everything is perfect, but it seems unnecessarily harsh. Also it should be more clear if a project function needs to be able to accept say, 2 AND 0 inputs or if you can choose to allow it to accept 2 inputs or write it to prompt the user for input. What I just said could be very unclear, though. 39.  The class should have a book 40.  I just personally don't like matlab as much as excel 41.  The class was good. I learned a lot in a relatively short amount of time, and in working the projects I was able to solidify what I learned. 42.  It was extremely hard, for me at least, to be a two credit hour class. I spent more time on this class than most. All TA's were extremely helpful though. 43.  I thought the labs were kind of lacking on examples. They had a bunch of trivial information and several overly complicated examples that were hard to follow but I thought they could use many more simple examples.Plus the projects were a pain and took a lot of time and effort for a 2 hour class. 45.  Sometimes it is hard to understand how to format commands based off of the labs on the website, but I am not sure how to make that better. 46.  I had a really difficult time in this class. I really just felt thrown into the world of programming without much instruction. I realize the class started slow and became increasingly more difficult. This was the most difficult class I have a had in college thus far. 47.  MATLAB is pretty confusing, it would help a lot if the TAs were more informed on how to do everything 48.  I really enjoyed this class and the projects were very challenging and helped me learn a lot more about matlab. 49.  More detailed examples online as well as slower explanations in class would be nice. I'm relatively quick but sometimes I really had trouble keeping up with the TA. 50.  Bind the end of the semester I have really enjoyed the class. The final project has been a clear indication for how much I really learned throughout the semester, and the usefulness behind matlab as a tool. Although confusing at times, EF 230 proved how matlab can benefit in an engineer's future study. 52.  Too fast and less number of TA's to help in the help sessions. 53.  I think that a lot of that labs had way too much crammed into them, so it was incredibly difficult to actually learn the material for the day since we were just rushing through it all. 54.  THIS IS LONG, BUT PLEASE READ. IT IS A LONG THOUGHT OUT CRITICISM AND SUGGESTION I do not believe that this class should be taught by TA's or in the "lab" layout that it is currently in. I have had a very difficult time translating the "definitions" that we learn in lab and then applying them to actual programing. From what I know of other friends who are programmers, they describe coding as a mind set. The way this class is taught is as a dictionary. The labs teach us functions (definitions), examples (use of word in a sentence), and topics related to the function (synonyms), and then expect us to write complete programs based off of this knowledge. To me, a person with no previous coding experience, this is like learning English for the first time and then being expected to write an essay. Instead of being taught by TA's and being based on a lab format, I believe this class should be taught by a professor in another format. I way that I think would be beneficial for learning, would be that of constant programming in class. If every class is set up with a single program that has to be written and the professor teaches different functions throughout the program, this would not only encompass the same curriculum, but also teach the mind set of coding as well as keep students attention due to the need to constantly type to stay on pace. This would provide students with their own programs and their own definitions instead of the general, unspecific definitions that the labs provide. 55.  I learned a ton about matlab which is valuable, I really enjoyed the class. One negative was that I felt that sometimes the work load was a bit too much for a 2 credit hour class. 56.  N/A 58.  One of the best classes I have ever had, if not the best. The final project is the best project in my academic career to sure. 59.  Projects were extremely hard and almost impossible without help. Not enough time on tests. 60.  Could include an option for a small textbook. 61.  The class was as a whole was enjoyable. I really like Matlab and the projects were the most fun part about the class. The amount of work or the time expected from us was never too much. One suggestion I have is to have the TA's move a little slower through the example problems in the labs. Sometimes, I could not keep up with them. Other than that minor suggestion, I have really enjoyed the class. 62.  Great class, structured well. 63.  Beginning the board was too dark, it improved only in the last two classes 64.  The only thing that I would suggest is to go a little bit slower 65.  The only reason to come to lab is the attendance grade 66.  This class does not give us a working knowledge of matlab. Our previous matlab course (105) gave a tiny, non-functional, basic foundation of matlab, and this course attempts to build a mansion on that. There is too much material and not enough time/instruction to learn it. It is good that we can reference back to the labs, but this does not mean that we can remember everything. 67.  The class could have better teaching results if the professor didn't let TAs teach the class. 68.  The class went in to a reasonable depth of the material. TA's were helpful and attempted to keep class exciting. 69.  The projects took way to long for a 2 hour class. 70.  The pace is good. The projects are interesting. 71.  Great material covered at a good place 72.  a lot of workload 73.  Maybe work more complicated example problems in class, instead of straight-forward ones, so students are ready for higher-difficulty questions like those presented by projects and tests. 74.  I think the professor could have done a much better job teaching this class. I was not able to learn very well from my TA's. The lectures were not very effective because they are taught by TA's. 75.  Overall, it is a fairly well rounded course. The homework is reasonable. The projects are assigned with enough time for us to complete and do well on them. The TAs are able to answer most of the questions given. 76.  I did not like this class; however, I don't like matlab in general. Studying for these exams was impossible, as I always would need help to figure out programs when studying. Also, this was a ton of work for a 2 credit hour class. 77.  good 78.  Possibly restructure the format of the class but i'm not sure how. 79.  Become a three hour class if there are going to be 15 hour projects 80.  The class was very difficult. I think that we were given short lessons and expected to know much more than what was covered. Projects took forever because of that reason. There should be more practice problems on the homework. Not just concept questions! 81.  More detailed in class examples. 82.  It was a FUN class but it would be better if i got a A 83.  Was a great class, and very helpful. I will now use Matlab for much more outside of this class. 84.  Class always went on tangents on random subjects and moved rapidly or slowly indicative of poor preparation. Also please get a new projector so we don't have 2 weeks of hard readings. 86.  The class was decent. I feel like I didn't learn as much as I should have for the amount of work that was required for this course. 87.  Honestly, I think the suggested work for this class is not advantageous to the student's learning. I felt extremely pressured to just finish the work instead of actually learn it because I didn't want to get behind in the material. I am a very slow coder and I struggled in this class because I felt like I didn't have adequate time for projects and tests. 88.  Awful...just awful. 89.  Had a difficult time relating to the material. 90.  This class was awesome! It was my favorite class of the year. The TA's did a great job and devoted a lot of their time to help us succeed. 91.  I honestly feel like I had to learn on my own. Better TAs who actually care would be helpful. 92.  We needed more time for project. 93.  The beginning of the semester was a lot more helpful and I learned a lot more than what I learned around after the first test. The TAs were not ready for the lecture and the idea of having TWO TAs was not a good idea. they don't know which of them should teach what subject. It made the course harder. I think just having one person fixed on the computer and the other one teaching the entire semester and they don't change place at all would be better for both the TAs and the students. 94.  Make the air conditioner in the back quieter, I couldn't hear any of the lectures. 96.  In the future, I would try to make the labs more engaging. 98.  A little fast interesting fun at times 99.  Go over the topics in more detail- don't just skim over it and assume we get it right away so we can get out of class early. 101.  The required work for this class is sometimes more difficult, or on topics that are not covered in class. That could be altered by either making the class more in-depth (more hours) or making the exams more like what is done in class. Other than that, the material covered is very helpful and I enjoyed the class overall! 102.  it's fine 103.  This class is very hard. It is like learning a new language and sometimes it takes folks longer than others to actually learn a new language. 104.  Would liked to have seen more gui oriented matlab designs. Block diagrams and flow diagrams seem very useful in engineering. Also, if time would permit it, having a lab based project where we test a system manually then interpret the results using matlab. 105.  I thought it was useful, pretty much all my learning came from figuring things out on my own, not so much from paying attention in labs. TA's were helpful though, when needed 107.  Some of the class time is wasted or underutilized. 108.  This was a really cool class, and I learned a lot of interesting things. However, I think there was extremely too much out of class work to just be a 2 hour class. The projects need to be simplified or something. 109.  Easy for people who already know how to program. Wouild be legit if there was an honors portion. 110.  The coding test questions were occasionally too difficult and could have used to be less time consuming and more specific. 111.  It was a good experience and i am more familiar with matlab but i felt very lost in many classes and did not understand some of the material. There is a very fast pace to the class and it feels like some material was crammed in. 112.  suggestion - cover more in-depth examples in class; the homework can be extremely frustrating when it asks about commands that we have no information on, even in the lab on the website 113.  No one seemed willing to help when I had questions. 115.  TA's were great and very helpful! 116.  The class was informative. I am not very good at Matlab, but this class taught me a lot more about it. 118.  The topic is difficult to teach but the ta's did a very good job in conveying enough to make the homework sensible. I would suggest more homework (weekly) and maybe one less project. 119.  I believe this class was very well presented and formatted. Students had every opportunity to do well. 121.  Hope we could have been given more instructions on the project. 122.  Sometimes I was lost, but overall good class. 125.  The TA's could have explained things a little simpler. 126.  Projects were very hard. Exams were okay, but sometimes coding questions were difficult. i liked the layout of the labs and the homework was helpful. 127.  At times the class seemed to drag on without a reason... 128.  The class is very well structured and the amount of material I have learned about Matlab has been pleasing. At times, however, it seems the workload does not reflect the amount of credit hours the course is worth. 129.  This class should be a three hour class. I think that I put in just as much time as effort (even with the open note tests) as my other three hour courses. 131.  The User Interaction lab (lab 12) needs more information on menu customization. 132.  This class was overall very successful. Engineering Fundamentals does a very good job compared to any other classes we take. Honestly it could not be made much better. It would be nice to learn how to make games and use simulink a little more but overall great class. 133.  I think the updates for the final project being due before the project itself was a good idea. 135.  The course was confusing because there is so much material that was trying to be covered that it left the people in the dust who did not understand or that were just slow. 136.  Loved it. I never knew how much I liked matlab until taking this class, but now I program in matlab for fun. 137.  This class was relatively tough for me, but you all did a great job with the presenting the information well. Maybe give a little more detail when describing the projects. 138.  Challenging, but overall I learned a lot. 139.  Make all the tests like the 3 one 141.  I thought it was very helpful information that we needed to know for our future classes. 142.  Had a hard time keeping up with code during class. It was a little fast for me. 143.  A ton of material to memorize and some projects did not have enough information given about them sometimes I felt that class was a little unorganized 144.  Class went very quickly at times and was taught with the assumption that some students already knew some things when some didn't 145.  I actually enjoyed coding, although i think the grades should be based on the projects more than the tests. 146.  This class was very challenging for me. It took going to many help sessions and outside learning to be able to understand the material. 147.  Having a hard time with the background and applications of matlab coding. I feel that maybe it could be better explained. 148.  I thought some of the key concepts used in exams and projects were not addressed how they should have been. I thought some concepts should have had more focus. 149.  The amount of work for this class seems like a bit much for the number of hours it counts as. Having multiple 10 hour projects as well as homework for a two hour class seems incorrect. Maybe change the number of hours the class is rated as or make the amount of work more fitting. 150.  I don't think this class needs to be an overall engineering requirement. I think it should fall strictly into the computer science realm. I think that it would be far more beneficial to take a class that taught how to code in general, like java or html, because those concepts could apply to a wider variety of applications, whereas learning how to use matlab really only applies to matlab itself. Although I do confess I really have no idea what I am talking about when it comes to computers. 153.  Needs to be redone. It is very unorganized. Also the labs do not teach you what is on the homework. Make the labs more informative. 154.  Not all students can easily understand programming concepts. I feel like this class expects you to easily understand topics with little explaination. Also the coding grading is very nit picky 155.  N/A 156.  I'm aware that the structure and format of things needs to be what you ask for, but it is ridiculously constricting. It feels absolutely terrible when you can successfully program something, only to get an 80 on it because you didn't detail a function correctly. 157.  N/A 158.  make the final project just one project instead of 3. make it like a game that has to be like a minimum of like 400 lines of code. 159.  The explanations could have been more in depth to help with people who are slow to Matlab, like me. 160.  SLOW DOWN 161.  It was a very good introduction to computer problem-solving. I thought the sequencing was pretty good as well. I only wish we had spent more time on importing and exporting data. That's the one area I still have trouble with. 162.  I didn't learn nearly as much as I was expecting to. I learned how to code for very specific scenarios and that's it. I don't know how to asses a situation and when to use what specific functions. Overall, I was disappointed. The projects barely had any material that was taught in class. My section's averages for just about everything are usually the lowest and I honestly don't think it's fair to us. 163.  None 164.  Projects were a good mix of fun/learning, homework was a good difficulty. I'd suggest more in class help for projects. 166.  I felt like some of the concepts that were used on the projects could have been more thoroughly explained. 168.  The TA's don't always teach very well. More, easier numerical answer problems would be better. This would allow the students to see more practical examples. 169.  This is a very difficult course, but that being said, I considered it somewhat fun in learning this material. 170.  At times, I think the class was more catered to the individuals that Matlab comes natural to. I am not naturally good at it, so it took me a lot longer to do every project and catch on to everything. The lectures are a simplified version of everything we see, and at times it was tough for me to transition. 171.  At times it is hard to keep up, but TA's are very knowledgable about Matlab. 172.  I think that his class moves a little bit too fast and requires students to learn a little too much on their own. Still, a great class. The GTAs were great, and the material was interesting. Having lab example problems to go over was very helpful. 173.  Well instructed course, the TA's do a great job. The content just doesn't seem useful for many applications; my personal experience may just be atypical though. "Primary focus is on development of computer programs in a modern programming language to solve engineering problems." 175.  This class was very informative and I learned a lot. I knew very little about computer programs and how they worked before this class, and now I feel like I have a basic undertanding of how a computer program works and can write simple codes for Mat-Lab. I think this class will be beneficial for me in the future. However, I feel that the grading for this class was very strict, and you had to score very high on most if not all of your grades to do well in the class. I think there was a lot more multiple choice homework and test questions than there was coding questions, which meant that if you missed problems a lot more points were taken off your scores even if you had a general understanding of what the question was asking for. 176.  I thought there was a lot of useful information presented in this class that will be very beneficial for students in their future jobs. I didn't like how the class was only taught by TAs. It's hard for them to teach the information to students, because they aren't professors, they are students and they don't have the teaching experience that professors have. 177.  I feel more confident using matlab after taking this class. 178.  There were too many projects for a 2 credit hour class. This class took up more time than the credit hours were worth. Due to how spread out the homework assignments were, it was easy to lose track of due dates. 179.  Class overall was good, but TAs could speak louder 180.  Love the class, Learned a lot of new things. 181.  The material presented could be condensed in a half semester 182.  I thought everything was fine. A few more hints with the homework would be nice, though. 183.  I learned a lot, but for the amount of work, it really should be worth more than 2 credits. 185.  I thought the material was haphazardly introduced. Some members of the class were able to do very well, while others were not. We were provided with a very faulty foundation for Matlab. As you know, you cannot effectively build upon a faulty or weak foundation. 186.  Possibly see about making it worth more credit hours. There was a lot of out of class work involved for this class to only be worth 2 credit hours. 187.  tough time understanding the little details of MATLAB 188.  It was quite informational and covered many topics 189.  I thought that the projects were graded far too harshly. They didn't give any second chances and were not considerate of tiny mistakes even when the masses made those same mistakes. 190.  I feel that they try to go over way too much in too little time. you are expected to know how to apply things in matlab that you have never gone over. The excuse they use is, "we want to make sure you know how to use the help function" but it does not change the fact that alot of things on HW and tests are things that we never touched on in class. NEED MORE TIME ON FUNCTIONS,SUBFUNCTIONS, AND CONDITIONAL STATEMENTS FOR THE LOOPS. 191.  There were some labs that were easy and did not take the whole class while others seemed to be too long to cover in a single class which made it difficult to learn those more difficult concepts. 192.  A little bit quicker paced. Also, a more integrated website. Blackboard is bad enough as it is and it just becomes tedious sifting through the links here. 193.  I really enjoyed the class. Also guys should put the header for all turned m files under its own tab because currently it is hidden in a lab. 194.  While some things seemed to be disproportionately hard comparitive to the level of the class, it was interesting learning MATLAB code and should prove for a decent basis in at least the way to think if I ever want to learn a different type of code. 195.  I am probably not the best judge of quality for this class since I didn't understand all of the material particularly well but the teaching seemed to be on par with other classes I have taken. 196.  This class required alot more work outside of class than I think is normal for a 2 credit class. 197.  id say the projects seem to be not from what we are studying in this class, for the projects id suggest to use only the materials we are taking in the class and put in on our projects. 198.  It was alittle more challenging than expected but the TAs were good and made it kinda fun. 201.  The class moved very fast and it was easy to fall behind. 202.  I realize that the concepts of computer programming are very hard to teach, however I would benefit greatly from having an actual textbook. I was very pleased with all the opportunities for extra help that were provided. 203.  lot of work and time spent for a two hour class. learned a lot about matlab though. 204.  Make the class the material covered in class more like what is expected on the exam instead of just general idea 205.  Sometimes the in-class examples did not translate well to what we were supposed to know for homework or tests. 209.  Teach the materials that will be relevant to the projects. Some of the techniques we were required to know weren't even covered. 210.  The structure of the class could be chaotic at times. However, I see that as a result of the material. End-of-semester coding seemed to delve into vague generalities on what the code would ultimately provide. fmincon and ode45 were basically referred to as having this incredibly long help file, too many steps to incorporate into a lesson. We did what we could. The beginning of the semester was rather straight-forward in comparison. Yet again, do to the apparent ease of the coding.

Morgan Helton

Rate the overall quality of your interaction with Morgan Helton. If you didn't have any interaction with this person, use N/A.

23% (48/210) Very good (1) 22% (46/210) Good (2) 12% (26/210) Average (3) 7% (14/210) Marginal (4) 4% (9/210) Poor (5) 32% (67/210) N/A (0) Avg: 1.52, NZAvg: 2.23, sum=319, cnt=210, nzcnt=143

Rate the quality of Morgan Helton's presentation and explanation of the material. If this person never presented for your class, use N/A.

20% (41/210) Very good (1) 22% (46/210) Good (2) 8% (16/210) Average (3) 6% (12/210) Marginal (4) 3% (6/210) Poor (5) 42% (89/210) N/A (0) Avg: 1.23, NZAvg: 2.14, sum=259, cnt=210, nzcnt=121

Specific comments/suggestions about Morgan Helton (optional)

1.  go morgan 14.  n/a 20.  I didn't have him as a TA, but he was at every help session I went to and always was helpful and funny. 22.  Morgan made me feel like an idiot. Any question I asked I felt as if he was talking down to me. I helped someone next to me with a problem and it worked but then he ran into a problem later and Morgan told the guy, "if you want to get a good grade in this class, never listen to this guy." By the end of the year if I had a question and he was in here I simply wouldn't ask because i didn't want to feel like an idiot. 25.  He was very helpful when I needed help with projects and home-works. 27.  One of the most helpful TAs. He always helped me with my coding problems and taught me what to look for when my code doesnt work. 30.  I went to a makeup class in his section. He was 100 times better than my actual TAs. 33.  He knows how to make you think about what you are questioning about and find an answer with minimum assistance. 35.  Asked him for help in help sessions and such, very helpful 37.  He was the one to look for when seeking help. 39.  na 46.  He always helped me when I needed help on problems. Always willing. 47.  did not interact with him much so my vote should not be held very highly as a good representation of him. 48.  Did a very good job of explaining and answering questions. 49.  I didn't see a whole lot of him but he was always very helpful in answering questions. 50.  Morgan was a great help in his ability to clearly explain what could be done to improve an individual's code. I did not have him in a class setting, but I did find his help very useful in the help sessions. 52.  N/A 53.  He clearly knew the material, but he never actually answered any of my questions. 55.  Clearly knows way more about matlab than other TA's, always answered my questions and offered advice. 59.  Not loud enough, goes fast through lab and doesn't explain examples. 60.  Morgan is a matlab stud. Lots of engergy. 62.  Did a great job answer questions and teaching the material. 67.  He presents the material a little too fast. Couldn't understand at times. 69.  HE was awesome didn't answer questions but always pointed you in the right direction when you ask him something. 70.  Sometimes gets offtrack. But rarely. 75.  I liked how he didn't give us the answer, but instead made us think about what we did wrong and how to fix it. 78.  Morgan did a great job and was very knowledgeable about the class. 80.  Nice guy. He was definitely willing to help out. The reason for the average was that lessons were not always well prepared. Made lessons kind of confusing. 84.  Very extroverted and often inconsiderate 85.  Very straight forward about answering your questions and helping with problems. 88.  He was not helpful with explanations and did not present the material in an effective way. Somewhat rude, very condescending and impatient. 90.  Very helpful definitely knew what he was doing. 91.  He would go over everything so fast and not completely and not explain it on our level. 92.  talks little fast. 94.  He is a solid TA 99.  He was good at explaining things when he spent time on the lab, but sometimes he went through really fast to let us out early. 100.  Morgan is very skilled in MATLAB, but he is not very good at offering assistance when I'm confused about something. He often makes things much more complicated than necessary and this detracts from his usefulness as a TA. 101.  Morgan was exceedingly helpful when working on projects. 102.  cool 106.  Very arrogant. 108.  Morgan was very helpful and definitely knew his stuff. 110.  Excellent TA. Very able to spot wrong things in code. 115.  Wonderful TA! Did a great job explaining the material and was willing to answer any questions. 118.  Try engaging the students more in class. So many people would talk after class about how confused they were on some things. Otherwise, awesome job. 120.  Great lecturing, easy to understand 121.  Morgan did a good job answering questions, but I hope he can give more detailed explanation on materials during class 122.  none 125.  N/A 132.  na 136.  Asked him a question at a help session, I recall the answer being satisfactory, but he was extremely condescending. 137.  N/A 139.  N/a 141.  He was very helpful with my questions and he was always able to help me 142.  Didn't reply to email :( 144.  Did an okay job at explaining material. Often moved too fast through material though. 153.  Is not very helpful 155.  N/A 157.  N/A 158.  Goes really fast. But still a great teacher. 159.  Morgan is very helpful and lively in class. He could improve by not just telling us what the answer is, but telling us why the answer is that. 160.  He talks fast and types fast. I don't know how to type 100 words a minute and kinda makes me feel stupid. He is really smart but he tries to explain things like I have taken this class before or something 161.  Excellent teacher; made the class very engaging. Very helpful when I had questions. 162.  He was a good TA. The only thing was he expected more out of us than we knew how to do. We're not all computer science majors, and have barely dealt with matlab before, I'm not sure he quite got that. 165.  I feel like he was too cynical,and he aimed to please himself. He knew what he was doing though. 166.  I think he could go into more detail on the uses of different commands and functions. Overall is a very good TA. 168.  He didn't seem very interested in answering questions. Conceited. 170.  n/a 171.  He knows the course extremely well and gives you help when asked. 175.  Morgan could explain the Mat-Lab material fairly well, and when I asked questions on the discussion board his comments helped me figure out some homework questions. However, he did not have a very good attitude about helping students. I heard him say things like "I don't care" and to me that is not the right attitude to have as a TA. He was often very smart-aleck and would sometimes say unnecessary comments if you asked him for help. Other times he was pretty good about just helping you. 182.  He helped me on a few project days and I would consider him to be the most helpful TA. 185.  Morgan seemed to have an excellent understanding of Matlab and all the material we were responsible for. He helped me a great deal on several of the projects. His attitude towards helping students is how it should be. If you were trying hard to get it to work on your own, he would help. 189.  N/A 190.  Very helpful and pleasant person. Morgan is very personable and knows how to connect with you on a one-on-one basis. Probably a better one-on-one instructor than classroom instructor but he is pretty good in the classroom too. Willing to go the extra mile for students and it is appreciated. 191.  Don't talk down to a coworker in front of a class. 193.  Cool guy. Awesome TA. 194.  Morgan was very helpful and knew a lot about MATLAB. He was able to explain things so that I understood them and helped me with projects and homework. 201.  N/A 204.  N/A 206.  He was rude when I asked questions or did not write the program the way he would have done it, even though my way would still work too. 207.  Morgan knows his stuff pretty well.

Taylor Morris

Rate the overall quality of your interaction with Taylor Morris. If you didn't have any interaction with this person, use N/A.

31% (65/210) Very good (1) 21% (45/210) Good (2) 5% (10/210) Average (3) 0% (0/210) Marginal (4) 0% (0/210) Poor (5) 43% (90/210) N/A (0) Avg: 0.88, NZAvg: 1.54, sum=185, cnt=210, nzcnt=120

Rate the quality of Taylor Morris's presentation and explanation of the material. If this person never presented for your class, use N/A.

28% (59/210) Very good (1) 20% (43/210) Good (2) 5% (11/210) Average (3) 0% (1/210) Marginal (4) 1% (2/210) Poor (5) 45% (94/210) N/A (0) Avg: 0.91, NZAvg: 1.66, sum=192, cnt=210, nzcnt=116

Specific comments/suggestions about Taylor Morris (optional)

1.  go taylor 2.  She spoke well in class, and knew what she was talking about. 4.  She helped me so much!! and I am so thankful because sometimes Id be way lost or stuck on a project but I could email her and she'd help me understand my mistakes 11.  She is pleasant, but doesn't answer questions very well. She doesn't say "Here is what's wrong, how would you fix it?", she says "Here, let me do it." 13.  sometimes going through examples could have explained better what was going on in each step 14.  Taylor was a really good TA-she knew what she was talking about and whenever I had questions she seemed to know what she was talking about 16.  Loved having her as a TA. 20.  She always knew how to answer questions without giving me the answer. She is easy to listen to and can relate to the students. 22.  Taylor was honestly the best. She was always willing to help and made you feel like your question was important. I emailed her several times this year and she emailed me back within a couple of hours and was EXTREMELY helpful. Also she knows what she is talking about and can normally help you out in a couple of swift keystrokes! 25.  I very much enjoyed both TA's and I felt they did a good job with the class 26.  little fast but overall good 27.  She was very helpful. Her lectures were ok. She didnt always explain thoroughly enough. 34.  Helpful when I asked her for help. Did a good job for a hard class. 39.  na 41.  Taylor was very helpful both in class and in the help sessions. 45.  She seemed to really understand matlab and was very good at presenting it 46.  Always helpful. The TAs seem to understand coding very well. So this helps for helping us with problems. 48.  N/A 49.  I think Taylor was trying to make us figure things out on our own but she didn't do it very well her explanations were always vague and sometimes misleading. I feel like she knew very well everything she was teaching it's just that more explaining and less hinting would be nice sometimes. 50.  Taylor did most of the presenting in my class. She was very clear in her presenting of new material and was always willing to answer questions and help in clarifying gray areas of particular coding parts of projects and others aspects of the class. She obviously knows her information and clearly displayed an interest in helping others learn. 55.  Very knowledgeable and always ready to help out 58.  Taylor is a very, very nice person. 69.  I dont think i had any interactions with her. 70.  N/A 79.  Most helpful person!! 102.  never met her 106.  Friendly and helpful. 118.  na 119.  Great about returning e-mails in a timely mannor 122.  none 124.  very helpful when you ask for guidance. 125.  She could have explained things a little simpler. 127.  Super helpful and always willing to help 129.  Taylor's awesome! 132.  Very helpful 136.  Did a good job of presenting the material. Seemed confident and knew the material well. 141.  She also always helped me when I needed help 145.  I think she is very good at explaining things, and she definitely knows what she is talking about. 147.  Taylor always seemed to know what she was doing and I was satisfied whenever I asked her a question. Only briefly experiencing the other TA's in help sessions and such,I definitely felt most comfortable with her. 148.  She did a good job, and she did her best to help everyone to the best of her ability. 155.  N/A 157.  N/A 158.  N/A 160.  She has helped me before and she is really nice and helpful 165.  I feel that she was well knowledgeable about the subject and did what was necessary for us to learn. I did not feel she went above and beyond she did only what was expected and no more. 168.  Very willing to help. Cheerful. Could be more clear in explanations. 170.  She is my favorite TA. She always takes the time to help you, and she will not leave until you have figured it out. It is definitely obvious that she knows what she is doing, and she is willing to relook stuff up if she doesn't know immediately. 172.  Great job! Great understanding of the material and ability to explain it. 175.  Taylor was awesome! She would always take as much time as needed to explain anything from concepts to technical aspects of Mat-Lab programming. She always answered e-mails, would help you debug, and always smiled and seemed happy when she was interacting with you. She would help no matter how trivial or complex the problem and was very very kind. You could tell she had a great understanding of Mat-Lab and I really enjoyed being in her class. 183.  Gave me some good hints for my interview with L3. 184.  She was very helpful with all my code hang-ups, a quality TA. 185.  I think Taylor had a very good understanding of the material presented and she was very helpful one on one. On the other hand, I thought she was not good at presenting the material. She seemed to not want to be there at all, she was very monotone and not an interesting instructor. 187.  n/a 188.  She was extremely clear when assisting me with problems and was able to guide me through solutions. 189.  Very helpful and nice. 190.  n/a 194.  N/A 201.  Extremely helpful and very nice. 204.  N/A 206.  She was a great help in class and out of class. She was really easy to approach with questions and was quick to help in a way that was easy to understand. Great teacher! 210.  Taylor seemed to have a pretty intimate understanding of the material (computer engineer?). She was readily able to simplify a concept, when the explanation became too muddled or obscure in the documentation.

Jake Brisby

Rate the overall quality of your interaction with Jake Brisby. If you didn't have any interaction with this person, use N/A.

17% (36/210) Very good (1) 25% (53/210) Good (2) 7% (15/210) Average (3) 1% (3/210) Marginal (4) 0% (0/210) Poor (5) 49% (103/210) N/A (0) Avg: 0.95, NZAvg: 1.86, sum=199, cnt=210, nzcnt=107

Rate the quality of Jake Brisby's presentation and explanation of the material. If this person never presented for your class, use N/A.

12% (25/210) Very good (1) 22% (47/210) Good (2) 14% (29/210) Average (3) 1% (2/210) Marginal (4) 0% (1/210) Poor (5) 50% (106/210) N/A (0) Avg: 1.04, NZAvg: 2.11, sum=219, cnt=210, nzcnt=104

Specific comments/suggestions about Jake Brisby (optional)

1.  go jake 2.  Didn't know as much as Taylor and always asked her for help if a student had a question. 11.  Jake's explanations of errors are a lot more informative. 13.  sometimes going through examples could have explained better what was going on in each step 14.  Jake was good. Always very helpful when asking questions and always knew what he was talking about 15.  When asked for help, he was good at covering information needed in the projects that was not covered in the labs (or not covered well and thoroughly). 16.  A little quite and let Taylor cover most material, but knew the material and could present when needed. 20.  He was helpful during the help sessions, but was a little quiet. 22.  Great guy, seems to be happy and willing to help. 25.  I very much enjoyed both TA's and I felt they did a good job with the class 26.  Good explanations 27.  Was sometimes helpful. Did not always offer an explanation to things. 34.  Very helpful. Also did a good job teaching a hard class. 39.  na 41.  Jake was very good at describing and working problems in class. 45.  He was always very helpful in the class and easy to learn from 46.  He was always helpful when I needed it. 48.  N/A 49.  Jake was helpful he just didn't do a whole lot in the class 50.  Jake obviously knows his matlab information. I would have liked to see him present more in class. It seemed as though Taylor did most of the presenting, but Jake could present just as well. When asking questions, Jake was very helpful in answering them clearly and in a way that could be understood by the student. 53.  He did not always know how to do everything in Matlab, but I thought he was incredibly helpful. He would at least try to figure it out along with me. 55.  I felt that he was a little unsure of his knowledge of matlab so he was often timid when answering questions, should be more confident 65.  Sometimes would just walk through code without expanding 69.  HE was available to help even when he wasnt on campus he would trouble shoot me over email. 70.  N.A 90.  He mostly just did the typing on the computer in my class not very much presenting. 91.  He just followed what Morgan wanted to do. 102.  never met him 118.  Great job but needs to actively lead the class more. 120.  good lecturing and explanation/help for problems 122.  none 132.  NA 141.  na 153.  helpful with coding 157.  N/A 158.  Very Good. 159.  Often times I ask Jake for help and he looks at my work for several minutes before asking Morgan to figure it out. 160.  He is fast too but he is a little more personable 161.  He and Morgan made a great team. Also did his best to help anyone with a question. 162.  The few times I had to ask a question, he was extremely helpful. 165.  He was a very good TA. 168.  Helpful and friendly. Not super quick with matlab. 170.  At times he seemed to really rely on Taylor to explain the material. But he was always really nice and willing to help, even if it meant looking things up from the past and talking it over with other TAs. 171.  Very easy to talk to but can be hard to follow when explaining material. 172.  Great job! Helpful and very personable. 175.  Jake was very nice when I needed help and his suggestions were often pretty good. He helped me out a lot on a problem with my Data Analysis Project Code and I was very thankful for that. 183.  Very willing to help during class. 185.  My comments for Jake are the same as they were for Taylor. My one on one interactions with him were very good, however his instructional abilities were less than average in my opinion. 187.  n/a 188.  Jake was very helpful and had a positive attitude when assisting someone. 190.  Jake is a good instructor but has a hard time connecting some times with students. He gets a little boring at times but is very good one-on-one. Needs to take charge a little more and get a little personality when he is doing classroom instruction. 201.  Don't pop your collar. 204.  N/A 206.  Great at instructing and answering questions that I had. Very helpful 210.  Jake may have been so laid-back as to be unremarkable. I do not recall many times where he exceeded or failed to meet expectations. So, I will put that down to a thoroughly adequate job-well-done.

Myles Smith

Rate the overall quality of your interaction with Myles Smith. If you didn't have any interaction with this person, use N/A.

23% (48/210) Very good (1) 20% (43/210) Good (2) 4% (9/210) Average (3) 1% (2/210) Marginal (4) 0% (1/210) Poor (5) 51% (107/210) N/A (0) Avg: 0.83, NZAvg: 1.69, sum=174, cnt=210, nzcnt=103

Rate the quality of Myles Smith's presentation and explanation of the material. If this person never presented for your class, use N/A.

17% (36/210) Very good (1) 17% (36/210) Good (2) 7% (15/210) Average (3) 1% (2/210) Marginal (4) 1% (2/210) Poor (5) 57% (119/210) N/A (0) Avg: 0.81, NZAvg: 1.88, sum=171, cnt=210, nzcnt=91

Specific comments/suggestions about Myles Smith (optional)

1.  go myles 14.  n/a 30.  He helped me a lot in the help sessions. He was able to explain things well and was extremely helpful. He was awesome!!! 31.  Was very helpful when it came to explaining in depth. He is only one person so questions sometimes went unanswered. 39.  na 46.  I never met Myles. I don't know. 48.  He also did an awesome job. 49.  I didn't really have much interaction at all with Myles 50.  At the help sessions, Myles was very helpful in aiding in understanding what to do next in a particular project. 55.  Always extremely helpful on projects, was able to look over my code and understand it right away 59.  Not loud enough, goes fast through lab and doesn't explain examples. 60.  Myles was a new TA for the class, but he jumped right in and did well. 62.  Did a great job answering questions and teaching the material. 67.  Didn't do a very good job explaining questions and material to the class. 69.  Very knowledgeable about matlab. 70.  Knows what he is doing. 75.  He was very helpful with every question I had for him, and was very knowledgeable of matlab. 78.  A great TA and did a great job teaching matlab 80.  Nice guy. Again same comments. Class lessons not always well prepared. 81.  Mumbled a tad bit sometimes. 84.  Need to speak up more 85.  Very helpful with answering your questions and takes time to help with your problems 91.  He gave me wrong instructions for project 2. I had to go back and redo it differently at the last minute. 92.  Speak little louder 94.  Worked well with students. 96.  I was impressed with both Myles knowledge of matlab and his ability to explain what he knew to others. 99.  He was nicer. 100.  Myles was generally helpful with explanations and instruction during class. He was personable and helpful when I was struggling. 101.  Myles was very good, not as knowledgeable as Morgan in some respects but still very helpful and understanding. Great TA. 102.  cool 106.  Helpful 108.  Myles is super awesome. He was always extremely helpful! 110.  Very knowledgeable and always willing to help! 114.  He worked really hard in giving us help and helped me understand matlab alot personally. Good job! 115.  Myles was a huge help with questions for the project! Wonderful TA, good at explaining the material, and willing to help always! 118.  na 122.  none 129.  Myles was so helpful for the projects! 132.  NA 141.  na 144.  Better job at explaining some material but didn't seem to have as good of a grasp on Matlab as Morgan 157.  N/A 158.  N/A 166.  Be more specific as to how some commands differ from the ones that are very similar. 168.  Very smart. Helpful. 170.  He just helped me a few times to point out small mistakes that I made. He was ready to help and knew what he was doing. 175.  Myles was very nice when I needed help. Sometimes he would not understand that because I had code didn't mean I understood it and when I wanted it explained to me he didn't understand that. But he often helped me out when I knew what my code was trying to do and needed help with it. 185.  N/A 189.  Very good with matlab troubleshooting 190.  n/a 193.  Great TA. He really knows what he is doing. 194.  Myles was also very helpful. He often explained things in a way that made sense if they didn't originally. 201.  N/A 202.  Myles is a great TA and explains the topics very well. He is very willing to go the extra mile to make sure the students understand. Overall I am very pleased with how he instructed the class and his willingness to help. 204.  N/A 207.  Myles was always very helpful and very nice about everything.

Will Schleter

Rate the overall quality of your interaction with Will Schleter. If you didn't have any interaction with this person, use N/A.

27% (57/210) Very good (1) 21% (44/210) Good (2) 5% (11/210) Average (3) 1% (2/210) Marginal (4) 1% (2/210) Poor (5) 45% (94/210) N/A (0) Avg: 0.93, NZAvg: 1.69, sum=196, cnt=210, nzcnt=116

Rate the quality of Will Schleter's presentation and explanation of the material. If this person never presented for your class, use N/A.

22% (46/210) Very good (1) 19% (39/210) Good (2) 3% (7/210) Average (3) 0% (1/210) Marginal (4) 1% (2/210) Poor (5) 55% (115/210) N/A (0) Avg: 0.76, NZAvg: 1.67, sum=159, cnt=210, nzcnt=95

Specific comments/suggestions about Will Schleter (optional)

1.  lazydog 11.  Doesn't interact in class, but he seems annoyed if he has to help during help sessions for projects. 14.  n/a 20.  He was in our class all day during Engineer's Day and helped me on my project. He said "I am trying to understand the way you are thinking hang on" as he thought about how to help me. Then continued to give me helpful hints when starting my project. 21.  made things more confusing than they needed to be 39.  na 45.  I wish I had gotten to be taught by him some because I know he is an excellent presenter and extremely easy to follow along with 46.  I never interacted with Prof. Schleter. So I don't know. 47.  Schleter is the man! I would have enjoyed it if there could have been one class period taught by Professor Schleter. 48.  N/A 49.  He wasn't around much but his explanations were always good. 53.  Always incredibly helpful with the projects! 55.  Helped out a lot on projects and answered my questions with precision. 58.  I probably couldn't count how many times I visited his office. I definitely could not count how nice and handy he was to be every time I visited his office. Really happy to have him as a professor twice in my career at UT. 62.  One of my two favorite engineering proffessors. 67.  Didn't really teach the class. I think he should have done more interaction with the class. 69.  SCHLEETTTTEEERRRR! 70.  N/A 79.  Sometimes ended up being misunderstood or confusing a student more when trying to help by trying to avoid giving the answer, but overall loved having add a teacher. 90.  Awesome professor! Always answers questions very thoroughly. 93.  Well!!! We just met him once or twice!! That is not how an instructor should be!! 114.  Worked hard for us and was quick on the answers on the discussion board. It was greatly appreciated. 115.  Didn't see him much, but he is a wonderful instructor. The class was well organize and the TA's he chose knew the material well. 118.  Professore Schleter is very fair with the students. 122.  none 127.  Helpful and always got the class involved 132.  Very helpful! 141.  na 145.  I had a great time in this class, and this professor definitely helps to keep my attention in class. 147.  I thought Dr. Schleter did a good job. Very easy going. I do feel that maybe some of the labs could be better explained and/or the labs themselves be update 148.  He did a great job. Managed time well. 157.  N/A 158.  N/A 165.  He was a great teacher when he taught, and very helpful outside of class. 166.  He was very helpful. 168.  Wasn't there. 170.  Rarely seen but always ready to help. Can quickly figure out the mistake as well. 175.  Professor Schleter is very nice and knowledgeable. I really learned a lot when he taught my class! I think he really helped a lot and was always willing to help no matter how small or large the problem was. 181.  Slowest presentation of material I've ever experienced. If you ask a rhetorical question, or a question that is clearly a joke, don't spend minutes of your students' time in silence while you wait for someone to answer it -- it won't happen. 183.  Of course we didn't have a lot of interaction with him during class, but he was extremely helpful during project help sessions. As always, even though the classes tend to be more work, the quality of the EF professors is far better than any other department I've interacted with on this campus. 185.  I wish Professor Schleter was more involved in teaching the class because I thought he was a great instructor in EF 151. My TAs were lacking in effective instructional abilities, so his efforts in teaching the classes would have made a big difference in my overall understanding of the material and my final grade along with many other members of the class I'm sure. 190.  came into our section maybe once or twice but never for more than a minute or two. 191.  Answered emails and questions in a timely manner. 193.  You were helpful in help sessions. 194.  Though my interaction was limited, Dr. Schelter was very helpful the few times I sent emails to him. 201.  N/A 204.  N/A 210.  I do not watch or care much for American "football", but Schleter always reminds me of Terry Bradshaw.

Brian Payne

Rate the overall quality of your interaction with Brian Payne. If you didn't have any interaction with this person, use N/A.

13% (27/210) Very good (1) 10% (20/210) Good (2) 4% (8/210) Average (3) 1% (2/210) Marginal (4) 1% (2/210) Poor (5) 72% (151/210) N/A (0) Avg: 0.52, NZAvg: 1.85, sum=109, cnt=210, nzcnt=59

Rate the quality of Brian Payne's presentation and explanation of the material. If this person never presented for your class, use N/A.

8% (17/210) Very good (1) 9% (18/210) Good (2) 2% (5/210) Average (3) 0% (0/210) Marginal (4) 0% (1/210) Poor (5) 80% (169/210) N/A (0) Avg: 0.35, NZAvg: 1.78, sum=73, cnt=210, nzcnt=41

Specific comments/suggestions about Brian Payne (optional)

1.  the dude 14.  I talked to him during help sessions and he was WONDERFUL. he always knew what he was talking about 20.  Brian was always extremely helpful. I didn't have much confidence in my matlab ability until he came up to me with encouraging words. His passion for matlab helped make help sessions fun. 22.  Ran into Brian outside of class and he helped me without my code in front of us. Smart guy, seemed like he really wanted to help. 30.  He helped me a lot in the help sessions. He was able to explain things well and was extremely helpful. 33.  Well spoken. Tries to help everyone he can, in an quick manner. 39.  na 46.  He was always willing to help in help sessions on practice exam problems and projects. 47.  Never saw this man ever 48.  N/A 50.  I never interacted with Brian, but in the computer lab, I could tell that Brian was very good in helping students who had found a road block in their projects or other EF 230 material. He seemed to be willing to help and a good resource of information. 53.  He also was really helpful with the projects and really seemed like he understood the material. He would make a good TA! 55.  Every time I went to the help sessions, he could understand my problem and read my code for errors and answered all my questions. 60.  Brain helped me several times in the 107 lab. He was very good at dumbing things down for me. 69.  Very good, knows how to teach you about what your doing rather than just giving you the answer. 70.  N/A 82.  NA 85.  Very helpful in the help sessions 90.  He was extremely helpful completing projects. 110.  Not as helpful as other TAs but still somewhat helpful. 118.  na 122.  none 132.  na 136.  Overheard him give students bad advice during a help session. Seemed to indicate a lack of understanding of the material being covered (good knowledge of matlab, but poor understanding of the problem being solved). 141.  na 157.  N/A 158.  N/A 162.  I talked to him a few times in the help sessions and he was pretty helpful. 168.  Awesome 175.  Brian was very helpful and would spend a lot of time explaining different parts of Mat-Lab to me. 185.  I only had one interaction with Brian, and personally I found it pretty frustrating. I had asked a specific question about one section of my data analysis project. My method of accomplishing this part of my code wasn't how he did it, so instead of trying to understand my rendition of it and trying to work with my code, he wanted to go back and make changes here and there and everywhere regardless of whether I understood them. 191.  Brian knows a lot about matlab, and always knew an answer to my question. Sometimes his answer was not the easiest or the best answer, but it almost always worked. (if only the same were true in the bike shop) 193.  His help sessions were great. He was helpful, but did not give you the answers. 200.  Brian Payne is the BEST!!! 201.  N/A 204.  N/A

Resources

Rate the overall quality of the EF 230 web site.

50% (106/210) Very good (1) 39% (81/210) Good (2) 9% (18/210) Average (3) 0% (1/210) Marginal (4) 2% (4/210) Poor (5) 0% (0/210) N/A (0) Avg: 1.65, NZAvg: 1.65, sum=346, cnt=210, nzcnt=210

General comments/suggestions on web site:

1.  to much homework 5.  Good organization of the website, great links, overall good. 7.  none 8.  Laid out in a very easy to understand way, no complaints. 10.  The website is well done and easy to navigate. 12.  Contrary to the UT site, I think the EF site is excellent 13.  good website, easy to navigate, user friendly 14.  The notes were extremely hard to follow. I think that with this kind of stuff a powerpoint would be useful. State a command or something and then the explanation of what it does and an example of it on a slide 15.  Very shallow and incomplete information 16.  Very easy to navigate and utalize. 18.  well organized 20.  This site is always great. 22.  Best website I work with. Who ever made this website should remake black board so that it is better formatted and just is easier to get around. 23.  Labs were explained much better on the 105 website. 24.  Well organized, helpful for referencing and learning new material. 26.  Web site works great and flows very well 27.  Good organization. Needs more examples of problems not covered in class. 28.  It doesn't seem to work on a smartphone, so I can't check things on the go. Otherwise, very well set up and easy to use. 29.  I don't think that there is anything I would change. Anyone who checks the site regularly shouldn't have any doubt about what's happening in class. 31.  Website works well, it was just like the site used in 151/152. 32.  Needs more MATLAB info, found myself looking up almost everything on Google because the website was pretty much useless. 35.  Easy to navigate 37.  It is incredibly well organized and has helpful links everywhere. 38.  Easy to navigate. Grades section is a little wonky - perhaps not make it average in grades that are available but haven't been completed as zeros? This makes it annoying to get a picture of your grade in the class. 39.  na 40.  The website is very well organized and kept up 41.  The website is efficient and helpful in working homework, projects, or just studying the material. 44.  It's very good and satisfies me. 45.  Best class website I have 46.  The website worked fine. The homework needs to be changed to a more interactive way of coding. Maybe the hw can walk students through code somehow. 47.  The website was helpful, but it might be more helpful if you could have uploaded more video walkthrough. When those were posted they helped a lot. 48.  N/A 49.  The coding parts of the homework's were a little ridiculous at times. 50.  The website has always been a great tool for a student. For me, the grade estimator has come in handy many times in evaluating where I stand in the class. The website is always clear in information for the student and very easy to maneuver through. 52.  Wish there was reminders you can set for each due dates 53.  It was really good, except when it would stop working! 54.  The web site is easy to read and navigate. 55.  Love it 56.  N/A 58.  Student should have a dropbox, like EF 105. 59.  Web site works very well 60.  none 61.  I could almost always find what I needed on the website and it was always helpful for doing the homeworks. 62.  Very well layed out and structured. Very helpful. 63.  Could include more information and examples. 64.  The website works well 65.  It's great 67.  Good website. Very organized. 68.  Small typos in the website are quite noticeable. 70.  It is organized. 71.  Most organized and best website I have seen for a class 74.  I do not have any issues with the website. Everything is easy to find. 75.  Very neatly laid out The only thing I can think of would be to occasionally add new examples to the labs. 77.  good 78.  Set up very well and great job 79.  Love how the website is set up. 80.  Everything I need to know is on that web site! it's awesome! 81.  Phenomenal 82.  NA 83.  The lay-out is nice. Maybe cleaning up the in-class examples page would help, but besides that I found it easy to navigate. 84.  Website was good. 85.  very organized, which is helpful 86.  All of the ef websites are great. Much better than blackboard and very easy to use 87.  Very straight forward. I think it's very well designed. 89.  Gets the job done. 90.  The website would unpredictable with sig figs sometimes. For instance on one problem it counted my answer wrong with 3 decimal points and counted it correct with 6 decimal points and other times it counted my answer wrong with 6 decimal points and correct with 3 decimal points. 92.  Everything is organized and easy to read 93.  It was really good, I don't think there should be any changes to it. Thanks for the web site. 94.  Nothing, love the web site setup. 95.  N/A 96.  Nothing really stands out as excellent or poorly built. I would leave the site alone honestly. 98.  easy to access 99.  none 100.  It's very user friendly. 101.  Sometimes the website has small errors (such as not listing interim due dates for projects on the calender). If this was done on purpose just ignore this! The website is great otherwise. 102.  its fine 103.  It is definitely easy to navigate. Also the website is very clear. the materials inside some labs are not. 104.  A better compilation of matlab files is needed. 107.  Best education website I have ever used. Absolutely fantastic, even better than "paid" educational websites. 108.  Very organized website. 110.  N/A 111.  The website was easy to navigate and i never had any issues 112.  overall, the website is a really good resource 113.  Very organized and laid out well. 114.  I like how organized and efficient it is. 115.  Well organize and easy to find things! 116.  The website was good! Easy to navigate/well laid out 117.  It was easy to use. 118.  none really. website layout was great. very easy to learn and navigate. 122.  Very easy to use. 123.  The mobile site is completely useless and unnecessary. The full version of the site has more features and is easier to navigate on most smartphones. 124.  good examples 125.  It is very helpful. 126.  Very well formatted, i like how organized it is. 128.  None. It does what it is supposed to do. 130.  It was good. 131.  It is the best out of all UTK sites 132.  Great website. Makes class that much better. 133.  The website was very reliable. 135.  The addition of the .m files was very nice. 136.  Well organized, very functional. I can think of nothing that needs to be changed. 137.  The website worked very well, wouldn't change it at all. 138.  Very well organized and always very easy to find what you need. 139.  Very good website 140.  Very organized and easy to navigate. 141.  I thought it was help but I thought not all of the homework questions were found off of the website. 142.  The site is good, but sometimes typos in the homework and labs could get confusing. 143.  Sites good 144.  the EF website is very useful and organized and was a huge help 145.  I love the structure that any EF class has because of the organization of the website. 10/10 would use again. 147.  Coming out of the class I feel that I struggled and worked decently hard but I also do not feel that I learned as much as I should've. That could be my ineptitude with programming of any kind, but I believe that maybe it was the class as well 148.  I think a few of the concepts need to be explained a little better on the website. The class is great, but since the student doesn't exactly have a book on the subject, I think the explanations of the concepts need to be expanded. 149.  Pretty easy to navigate and understand. 152.  e 154.  More in depth explainations for coding commands would have been extemely helpful 156.  I liked the website. The forums could be better. 157.  N/A 158.  Dont make homework problems over things that we didnt go over in class or cant find in that particular lab. 161.  Very easy to navigate and follow grade progress. There was only one time that I lost track of when an assignment was due. 163.  Easy to navigate and use 164.  The site is set up well and is helpful. My only suggestion would be to improve how you can search the m-file directory. 165.  It was well planned out 166.  It is very easy to use. 170.  really well formatted and easy to find everything 171.  Website is great and very useful. 172.  Organized, easy to navigate. A little bit monotonous though - everything is either a square or a rectangle! 175.  This website is thousands of times better than Blackboard! I wish the mat-lab example files and notes were organized a bit better but overall it is an awesome website and I really appreciated having it for a resource. 176.  There was a lot of information on the website that was extremely helpful for homework and test problems 177.  I have not had any problems using the web site. 178.  It is somehow a bit worse than the 151/152 websites, but still much better than blackboard. 179.  Always good, easy to find everything you need 181.  UI is outdated and there are endless mazes of links for class material 182.  I liked everything about it. 183.  Thousands of times better than anything else online at UT. 185.  The only bad thing I could say about the website is the lack of supplemental material. I personally need several takes on alot of this computer programming to understand it. Otherwise, it was just the same as the other EF websites, which I am very fond of. 186.  I really liked the inclusion of FAQ pages and specifically filtered discussion pages that were put up for the project after the first one. 187.  n/a 188.  It was not too difficult to navigate through the website 189.  Easy to navigate and userfriendly 190.  none 191.  Make sure the tests work. Although I was able to get the points for the question, I still wasted much of my time on that question. 192.  Mentioned above about the class. 193.  Love the website. The only thing I suggest is a search bar for the labs. Sometimes it is very hard to find specific things in broad and the many lab tabs. 194.  The only problem I ever had was on the thrid exam when it did not mark my correct answer as such. 195.  I actually love the way that the EF site in general functions. It makes it very easy to go back and learn material that you didn't understand. 197.  everything is perfect! 198.  It was put together well and easy to use. 201.  Very easy to use 202.  There is so much material covered in this class making the website very helpful when looking up questions in a quick manner. 204.  N/A 205.  I think the website works well and is a useful tool. 206.  Love the EF website. Wish it designed everything for UT 207.  The website is excellent 209.  Well organized with a good amount of resources. 210.  The website is perfectly adequate, devoid of incompatible plugins and reasonably well-laid-out. My only suggestion would be an automatic ticker or chat system for discussions, as opposed to the message board it often becomes.

What are your feelings on a textbook for this class?

7% (14/210) I would purchase a textbook if required (0) 20% (43/210) I would purchase a textbook if recommended (1) 73% (153/210) I don't think a textbook is needed (2) Avg: 1.66, NZAvg: 1.78, sum=349, cnt=210, nzcnt=196

Are there any other resources that you think might be useful as a formal part of this class?

1.  food 3.  video explanations for whenever you need refreshing on material, or of examples for homework problems 5.  A textbook would have been nice but not really required. 6.  no 7.  no, I think ef website is great. 8.  Nothing in particular 9.  no 10.  No, the mathworks website was used, and I think that it was helpful at times. Overall, the resources provided were adequate. 12.  I cant think of any 13.  lab material is sufficient 14.  A textbook and more and better notes 15.  Just improve the website. Don't make students waste money on unhelpful textbooks. 16.  No, the website is more than helpful. 18.  no 20.  I think it would be extremely helpful, there were many times where I forgot how helpful writing code on paper was and if we had a textbook it could be used as another resource away from the EF website. 21.  just a typical matlab handbook 23.  N/A 24.  No 26.  matlab help and extra info 27.  More examples of how to do different types of problems in class. Perhaps more explanations on how to do problems, the thinking behind the working problems. 28.  Some type of video working out problems would be nice, but not necessary. 29.  Between the help file and the website, my looking things up from other sources was usually minimal, except on the data analysis project. 31.  A book would be great. 32.  nope 35.  Not really, it was pretty solid 37.  A links section on each lab to information that is pertinent to the homework. 38.  Additional example problems. 39.  na 40.  a sheet/pdf of available commands and short descriptions would be very helpful 41.  We did not go over Simulink much and I think it would be useful to do more with that. 45.  Not really 46.  If this class followed a text book, I think would certainly help. 47.  nope, book sounds like a good idea though, shouldn't be required though 48.  No I honestly think the labs help you learn what you need to know. 49.  More help sessions would be nice 50.  I feel like the materials used for this class are perfect for the way the class is structured. With all materials on the computer, I feel that the addition of another resource, say a textbook, would have the potential of disrupting the flow of the class. 52.  POwerpoints for each labs 53.  I think that a textbook would be very helpful since it's hard to follow along with the TAs because they go way too fast sometimes. 54.  I do not know enough about other resources that pertain to this material that could be of use. 55.  I liked having it all online 56.  no 57.  No, the website and example files are plenty in my opinion. 58.  No! 59.  No 60.  none 61.  The MathWorks website is extremely helpful. 62.  No 63.  a book 64.  Do not make this class have a textbook. It is a waste of money. 65.  no. 67.  No 70.  I think the course is setup for success. 71.  Learning on your own 72.  google 73.  Video sessions of explanations of problems, like what was used in one project as a hint. 74.  no 75.  Another website that helps users operate Matlab. 76.  more help sessions 77.  no 78.  n/a 79.  Just Google. 80.  I think a textbook is a good idea. I struggled in this class, so extra help would have been great. 82.  NA 83.  I didn't really need any other resource for this class that I couldn't already easily get (Google, website, help sessions). 84.  Continuous online support if we work from home, also maybe more videos to help if we couldn't hear as well in class or see as well and we could also take it at a slower pace. 86.  Not that I know of 87.  More in depth examples and are applicable to suggested topics. 89.  None come to mind. 90.  no 91.  More help sessions. 92.  matlab help file 93.  No 94.  No, matlab is best taught through examples 95.  N/A 96.  I would create some sort of weekly review that allows those who miss labs to review the material from the previous week with a TA. I feel that that could have helped me to understand more of what is going on in this class. 97.  As many examples as possible, maybe from previous years 98.  cant think of any 99.  none 100.  No. 101.  I think a book that was used as a source for exam problems would be very helpful! 102.  no 103.  some of the matlab help found on google. I am unsure of specific names. 104.  Having an engineer come in and lecture on matlab and how he/she uses matlab in his/her work. 108.  maybe something for the projects 110.  The labs are helpful, but I do think that if there was some other type of structured material about the topics that we were covering that it would be helpful for review. Not to wordy and specific information. 111.  No not that i can think of 113.  No 114.  If the textbook was cheap, it would be very nice. It was very hard to find useful information on Matlab online. Alot of the articles were unrelated and had strange examples. 115.  No, the labs covered all the material that we needed. 116.  No, I think with the website (specifically the lab sections), everything could be figured out. 117.  I think that more online resources (other websites than mathworks) and examples of code would help. 118.  No. 119.  Matlab's online help forums 122.  none 123.  All I needed were the website and matlab help files. 125.  No. 126.  Maybe some matlab web pages. i used as additional resource such as mathworks. 127.  No most of the information for the class can be found online 128.  No 130.  Nope. 131.  fmincon function needs more examples 132.  None 133.  Not that I can think of. 135.  Solutions to practice exams. 136.  None. 137.  Maybe access to a sort of dictionary that make functions and commands make sense to normal people.. 138.  Google 139.  Web seminars offered by math works 140.  Not that I know of 141.  I don't think it so...just a computer 144.  not really besides the internet in general 145.  No, what was provided was fine. 146.  Possibly a MATLAB handbook that helps people understand the entire MATLAB program, including parts not covered in class. 147.  A book may be nice 148.  I don't know of any other resources that might be needed. 149.  Not that I can think of. 152.  e 153.  This class needs a textbook 156.  Not particularly. 157.  No 158.  as long as the homework questions come from the labs, no. 159.  None that I cna think of. 161.  If there were a MATLAB guide book, that would definitely be useful to have. 163.  None 164.  Maybe more program reference guides that are easily accessible. 165.  Just requiring a text book. 170.  no, i think the resources available now are good enough 171.  The projects seemed a little too difficult if you weren't great Matlab so I would make them a little easier. 172.  Might be helpful to have optional Friday review sessions. Also, no 8:00 classes please! 174.  The MATLAB website. 175.  I think Mat-Lab websites from other universities might be helpful. I don't find the Math-Works and Mat-Lab help websites very helpful most of the time. 176.  I thought the website was detailed enough to help with any questions we had 177.  No. 179.  The MATLAB website itself, it's really helpful 180.  I think the website is enough 181.  No 182.  No. I think the website successfully covers everything we need. 183.  not really. maybe for some of the stuff, clearer explanations on how to use the commands (especially more complicated ones like fmincon and maybe even early on loops) 185.  Engineering Computation with MATLAB by David M. Smith. There should have been assigned readings from this book. 186.  Not really. Pretty much everything necessary is already available via the website. 187.  n/a 189.  Better examples to prepare you for tests. 190.  none 191.  no 192.  No, the mathworks cite is enough. 194.  No 195.  More examples that are closely related to the homework. This usually wasn't a big problem, but sometimes when I was trying to understand how certain commands worked or how multiple commands worked together it was difficult not having a step by step guide. 196.  No, but I think the textbook is a big one! 197.  Matlab website only 198.  No 199.  Not that I know of! 201.  Tutorial videos 202.  No. 203.  no but I do think having a book with examples could be very helpful. 204.  None 205.  not really 206.  No. The Mathworks website is sometimes helpful 207.  nope 210.  An introduction to the online Mathworks documentation, which has helped me more often than not.

Suggestions

From your viewpoint, what was good about this class?

1.  nothing 2.  The layout was pretty decent. 3.  the beginning few labs 4.  Matlab is annoying at points but I can tell why it is useful and needed. 5.  The class helped me understand more about the material a little bit. 6.  The way it is set up 7.  I think everything was good. We had good teaching assistance and we learned lots of new things about matlab. 8.  Online homework 9.  cool things were learned 10.  The projects we worked were great practice in problems that may 11.  The homework and exam format. 12.  It give a great introduction in matlab which i think will be very useful 13.  The TA's were did a good job. 14.  I'm really bad at programming but it still is an interesting class and the TA's tried their hardest to keep it interesting. 15.  You could pretty much do the class online from home. 16.  The assistance given when I needed help. 17.  Easy to get points. 18.  Helped me learn my way around matlab 19.  Having projects before the exams were extremely helpful for the exams since they had us using what we had learned. 20.  The ability of the TAs to never just give us the answers. 21.  the TA involvement 22.  I learned a lot about matlab, and it is very powerful. I like the last project because it really shows me that matlab can be practical in my other courses. 23.  Projects were ok nothing was particularly spectacular. 24.  Some useful skills for computations using Matlab 25.  I learned how to proficiently use matlab 26.  Gave me a more in-depth understanding of Matlab 27.  The help sessions were really helpful. I learned the most from one on one with the TAs. 28.  The information learned was overall very good, as well as the problem solving method employed. The TA's were very competent. 29.  I liked getting to make 30.  This was a 2 hour class that I spent over 6 hours on a week. Somethings just didn't add up. The good part was, I learned matlab. 31.  The projects require you to think more then the homework; gives students good coding practice. 32.  The TA's were good and seemed to know their stuff. 33.  The layout of the grading and accessibility of help. 34.  Helpfulness and willingness of TAs. 35.  some of the projects were fun 36.  The material will be helpful in the future. 37.  The structure of the website and independent centric projects 38.  The relative ease and ability to look up what you needed. The lack of requirement of stringent memorization (the open nature of the exams). I complain about how some things are confusing to look up but on the whole I view it as solid. Perhaps some more open-ended projects like the one we had this year - more options in terms of ways to complete it. (I realize it doesn't work as well for writing code to batch process a bunch of directories, for instance, but I prefer to allow the user to designate input as opposed to making a function with inputs). 39.  na 40.  The informality of "getting your work done" is much more important than "listen and die of boredom" 41.  The projects were the best part of the class in my opinion because they helped me learn the material while practicing for the exams. 42.  I have no previous background with any type of programming so I did learn a lot. 43.  ... 44.  Website is good 45.  It is well organized and I like how everything you need is on the website. It is hard to miss something you need to know 46.  I think it is important to learn how to program so I think it is an important class. 47.  giving me enough info on matlab to help me with other class work 48.  The projects where challenging but the forced you to learn the material. 49.  Overall the class was good I had specific suggestions for each of the above sections on what would make it better, 50.  Although tedious, the online homework was very helpful in clarifying and teaching how to do particular problems with matlab. It also provided good practice for the exams. 51.  It was very challenging 52.  Everything in online and no textbooks needed 53.  I like the homework, very helpful for practicing our skills. The practice exams were also very helpful. 54.  The tests are fair and well formatted. 55.  That we could use hand-written notes on exams, I could write things how I understood them which was more helpful at times. 56.  nothing 57.  I thought the pace was good and the examples gone over in class were fairly helpful. 58.  It was interesting most of the time. It feels like you are solving riddles, which is very successful. Website is very clear. Examples examples examples, they helped the most. 59.  It has good intentions 60.  I liked the lectures and exam formats. 61.  The projects were definitely the best part because they took what we learned and put it in more of a real world context. 62.  The availability of materials, discussion board, help sessions, projects helped learn the material. 63.  there are two lecturers 64.  I liked doing the projects and think they helped teach the material the best 65.  Learning to code in practical ways. 66.  The exams were open notes/website. 67.  How well informed the website kept me. 68.  The self pacing nature, examples offered during class, test format. 69.  The Practice problems that looks similar to test problems, and basing the coding exam questions off a recent project 70.  The homework problems were relevant. 71.  The amount of material covered was the right amount. I didn't feel behind 72.  to know more about the coding in matlab 73.  The material was presented, examples were worked, and the homework was simple because of it. 74.  I thought it was good that 5% of our grade is made up of attendance. I also thought the homework was manageable. 75.  The in class examples helped the most in learning the material as well as the assigned homework. The TAs also did a good job in explaining the material. 76.  nothing 77.  the sample section is good 78.  The organization was great and know what to do was great 79.  Some parts of the projects really helped me understand the concepts. 80.  Teachers were super funny. I actually really liked them. The lessons covered so many different things. It was cool to see how much we can get matlab to do. 81.  The website structure was phenomenal. 82.  Great TAs 83.  Learning Matlab. 84.  Learning matlab isn't bad 85.  It is very organized and the assignments were given with a fair amount of time to complete 86.  The fact that this whole class was pretty much online was good. 87.  I was able to learn basic coding techniques and develop skills useful in my engineering classes such as systems of differential equations and matrix applications. 88.  nothing 89.  Scheduling. Did not keep me on campus late. 90.  The information was presented in an understandable way. 91.  It made me think differently. 92.  No text book required and everything we need is on the website. 93.  The web site. 94.  The projects were fun. 95.  exams are only 8% 96.  This class is very well organized. 97.  I gained a good understanding of very basic programing 98.  engineering specific topics 99.  I like that we can use the website and our previous work in the exams and that we can use the internet for help, as long as we cite our source in a comment. 100.  I have the potential to apply MATLAB outside of this class. 101.  The range of topics covered was excellent and taught me enough to be able to write my own program just from memory. 102.  the homeworks 103.  The TAs are good, and know what they are doing it. 104.  The mix of multiple choice and coded problems in homework was perfect. 105.  having a structure for going through features of matlab, good examples to work. 106.  The grading format 107.  I learned the ideas of computer programming. I enjoy the idea of computer programming because it is very logical and methodical and I enjoy the problem solving. 108.  All of the homeworks 109.  The flow of the programming curriculum. 110.  The interactions with the TAs are beneficial in learning as well as all the help that is offered. It can be challenging material for some people and all the help really aids in learning. 111.  It was good for introducing computer programming with matlab 112.  The class was good when we covered problems from engineering classes, especially the last module. 113.  The presentation of material 114.  The organization, knowledge of student requirements, and the help from the teachers and TA. 115.  TA's going over examples was the most helpful. 116.  I liked learning more about the Matlab concepts that I didn't know about and some of the projects. 117.  It was organized very well. It was for the most part always very clear when things were due. 118.  Matlab is awesome and powerful and entirely required for my degree. :) 119.  Well structured, objectives clearly laid out, no surprises. Good communication to students. Well presented and tests were challenging but fulfilling. 120.  the lecture and explantations of how matlab coding works. 121.  The materials I've learned are very very useful 122.  It was good to learn how to use matlab 123.  The projects were interesting and of appropriate difficulty. 124.  the examples 125.  The labs were very straight forward. 126.  The grade layout, and how the labs are laid out. I can find the information i am looking for very easy. 127.  It had lots of helpful mat lab uses. G 128.  The amount of material is maintainable and worthwhile 129.  The homeworks were really helpful and reinforced the lab of the day. 130.  Practically everything. The projects (Except for the image one) were good and helped showcase functions of MatLab we might use. And the homework was helpful. 131.  Being able to refer to matlab help and the labs for test is helpful 132.  Lots of examples and hands on learning 133.  The homework helped reinforce materials. 134.  This class was very informative. Very useful material. 135.  The program knowledge is nice and important. 136.  Introduced material well, and in an orderly way that made sense. Teaches commands for those who understand the basics, and basic understanding for those who need help with those. 137.  The example problems were generally very helpful. The presentation by the TA's and Schleter was always very insightful and made relevant to us. 138.  There is always extra help when needed and we are never really left to figure out hard material completely on our own. 139.  The presentation of the material during class 140.  It was enjoyable and informative. 141.  Being able to apply engineering applications to matlab. 142.  The amount of material covered was good. I learned a lot about matlab. 143.  Learning how to use more complicated programming was good and is a very useful skill taught me better problem solving 144.  The homework and practice exams were often very similar to the actual exams 145.  The class was structured well, and I liked that way the material was presented. It was great to give the students a try at using the new concepts during class. 146.  I feel like I learned a lot of new material in this class. Coming into this class, I did not consider myself good at MATLAB, but I am definitely much better now. I feel like the labs covered a wide variety of material. 147.  I enjoyed the projects. It was very challenging but I felt I learned the most from them 148.  The class covered a lot of material, preparing me for future classes 149.  The TA's are helpful. 150.  it had a decent tie in to solving engineering problems 151.  I learned Matlab 152.  e 153.  time management 154.  some of the lessons were clear. just some though 155.  N/A 156.  A good introduction to matlab. 157.  It helped me learn how to solve problems in a variety of ways 158.  The structure of the overall class was good. The amount of help and explanation that was given when needed. 159.  The class was rigorous so you really had to learn these things in order to get an A. 160.  Nothing. 161.  I liked how the class presented general topics about computer programming and problem-solving and then applied it to MATLAB and potential engineering applications. If I decide to learn a programming language, I think I'll pick it up a lot faster because of this class. 162.  The homeworks were generally good and made us think about the topics. The set up of the labs were good, however not all the TA's cared about the set up. 163.  The class was able to clearly explain most of the concepts, and if the explanation wasn't clear, the provided sample code was usually enough to understand it. 164.  The tests were something I felt like I could prepare for without being overwhelmed. 165.  I feel as though I learned a bit more about MATlab. The class was just to fast paced for me. 166.  The TA's were very helpful. I did learn a lot more about MATLAB. There was a lot of material introduced and the projects very much reflected it. 167.  The class's material was interesting. The help sessions were nice. 168.  Some of the tests were good. 169.  Learning how programs are written that are similar to those we use on the internet. 170.  It teaches you to think a certain way that an engineer should. You identify the task/problem and have to come up with a series of tasks to accomplish it. 171.  The homeworks were good way of measuring information learned. 172.  Interactive, ability to self-teach, personable GTAs. 173.  Instruction. 174.  The help sessions and the actual classes. 175.  I thought it was good that we got to learn about Mat-Lab by doing projects. I think doing projects before tests really helped me have a better understanding of the material I was going to be tested over. Trying to do the projects on my own then asking for help from other TAs and students really helped me learn and understand Mat-Lab better. 176.  I thought this class had so much information that we can use in our future job. 177.  The pace of the class was good, and the ability to schedule the final is great. 178.  The last exam format, where you could input your answer to the coding section rather than just a code. Much more straightforward. 179.  Not too hard, not too easy, just the right amount 180.  The website and the way to learn the material. 181.  Logical problem solving 182.  It did help me become comfortable with the matlab program. Which I am glad of because I have had to use Matlab in other courses. 183.  I learned how to do something that I didn't know before (MATLAB) 184.  This class is more productive than the class before it due to its increased meeting time. Also, the fundamentals of coding are helpful outside of matlab (I have applied this knowledge to writing excel macros, something I did not know how to do before). 185.  The only positive outcome of this class for me is to have learned how to utilize matlab for many different science and engineering applications. The experience as a whole was very frustrating and at times infuriating. 186.  How relatable the labs were to the homework and tests. 187.  I can use matlab a little easier and have used it for my other classes. 188.  I liked how organized the class was and there was always help when needed. 189.  I liked that you got to use google for the exams. 190.  the final project was good as it was very low pressure, but I wish it was more directed and not so open ended. 191.  Help sessions were very helpful/\. 192.  Great TAs, proper workload aside from projects, fair grading. 193.  I like the two TA thing. I very much enjoyed and learned from the class. 194.  The ability to go through the lab at your own pace and work on homework if you felt you understood the material well enough was nice. 195.  The skills being taught are very useful to the engineering field. 196.  From my understanding, I will need matlab in future classes, so it is good that I learned as much as I could! 197.  learning how to solve engineering problems using Matlab 198.  It was informative and helped me learn a couple more advanced matlab techniques than EF 105. 199.  The first half of the class. 200.  I learned that coding is a very complex but if broken down into little steps, programs become easier to produce. 201.  N/A 202.  Grading seemed fair, my TA's were personable and helpful 203.  liked the homework and projects a lot. found them very helpful in understanding the material. 204.  N/A 205.  For the most part, my interactions with the TA's were really good. 206.  The teaching was great 207.  There is plenty of help if you need it. 208.  Good references on the website. 209.  Learned a very good amount about Matlab and what it can be used for. 210.  I enjoyed the projects, lengthy as they became, especially the creative aspects kept for the sake of general sanity. The homework was also helpful, while being thorough, as opposed to a chore.

From your viewpoint, what was wrong with this class??

1.  everything 2.  The exams were a lot harder than any of the examples given in class. 3.  too much homework which we don't really go over how to work 4.  its only a two hour class.. there's 4 projects and 4 exams... I spend more then two hours worth of credit 5.  The TA's didn't teach the class very well, all they did was read exactly what was already on the website. 6.  The first two exams coding parts were tricky, i like the way the last exam was set up. 7.  Everything was good, except for the projects. The projects were hard and it took long time to do them. 8.  Labs were sometimes lacking in all the material we needed 9.  excepted way too much on our own; way too much time spent for a 2 hour class 10.  Not enough motivation. Classes were boring and generally uninteresting. 11.  Once again, hours upon hours of project work time for a 2 hour course is completely unfair. Also the grading is BS - the easier projects, which would help keep a higher project average, aren't weighted NEARLY as much as the harder projects. This means most of your project average consists of the grade you receive for more difficult projects, which makes it hard to keep a good project average. 12.  I didnt think the sound lab was necessary 13.  just making sure students know what is going on during example problems 14.  it should be geared towards what we will actually be doing later in life, not just a generalization 15.  The labs were not helpful, but unfortunately attendance is required. You are basically on your own no matter what. If you cannot find and teach yourself the material, you may not succeed in the class. The homework, projects, and tests ask for information not mentioned on the website. The MATLAB documentation and Google are better resources than the lab lectures and class website. 16.  The time it took to get assistance when I needed help. 17.  Too many exams for a 2 credit course. 18.  little gained in lecture beyond what can be learned independently from the material on the website and matlab help files 19.  fmincon was not covered very well at all. 20.  The multiple choice homework. 21.  didn't really explain how to go about solving large problems, rather, focused more on specifics which doesn't help when given more broad problems to solve... 22.  Honestly, Morgan really made me not like this class, for as helpful and cheerful Taylor was, Morgan counteracted that a lot. His approach really made me not enjoy coming to class, especially when i needed help with something and he was the only TA. 23.  Homeworks needed to be setup more like 105 and more TA's like Steve. 24.  Not much, I just didn't find the class interesting. 25.  A lot of the multiple choice hindered my grade and didn't add to my knowledge. 26.  Went a little fast and expected us to know tools that had not been taught in class 27.  We learned a lot really quickly. The projects were almost overly complex and hard to understand. 28.  Very little. Overall the class is very well formatted. 29.  Sometimes I feel like the real-world value of matlab is questionable. 30.  I had to teach myself all the material. I did not learn anything in the classes. I learned from help sessions and google. The class pace was too fast. 31.  I think the homework should be weekly coding problems. There wasn't enough interaction for us to understand the code, it was just presented and we had to figure out the rest. 32.  Required way too much time outside of class for a 2 credit class 33.  Project timing. 34.  A lot of things. It's an odd structured class. I never knew what to study for on the tests. A lot of times in projects we had to use random functions that we never even got close to touching in class. The list goes on and on. 35.  I don't think the lab on ODE45 was helpful at all, I asked for help and read the lab numerous times and still have no idea how it works 36.  The objectives for the projects were not usually very clear. 37.  The structured projects (2&3). They were boring and much more complicated than our labs even hinted at being possible. 38.  Required attendance. 39.  na 40.  I don't feel like it is relevant to my education: I will always just use excel, a calculator and hysis instead of matlab in the future 41.  I do not like the heavy presence of multiple choice questions on the exams and homework; I would rather have had the amount/weight of short answer to multiple choice to be flipped so that more work is being done with matlab than with the theoretical. 42.  There is too much to cover and not enough time to do it in. The TA's did their best to give us all the information in the class times but it felt rushed a lot. 43.  It was too time consuming for a 2 hour class especially from the projects. 44.  I chose wrong class. 45.  It is a little hard to keep up sometimes. The projects were a little difficult at times too but that very well could be my own fault. 46.  The class is a 2 hour class and the work required is well over that. However, I did poorly in this class so the fact that it was not more than 2 hours helped my GPA. 47.  the TA were sometimes not that helpful 48.  Sometimes hard to hear the teachers. They also went kinda fast. 49.  Not enough help sessions or actual examples gone through slowly in class. 50.  I didn't find anything "wrong" with the class. Many times homework and projects became burdens but as the semester is coming to a close, I have realized how much I have learned using matlab and taking this course. I find the structure of the class to fit perfectly and the components of the class to provide clear explanations of how to perform well in the course. 51.  We were forced to teach ourselves most of the material used on the projects 52.  Too fast and hard to see the screen in lectures 53.  I think that the material taught in the labs should be slightly harder. Many times it seemed like the labs and homework would be simple concepts of a certain subject that were easier to understand so I would go into the test confident of the material, but then the tests were just so much more complicated than anything else we had ever learned and I would feel completely overwhelmed by the required task. 54.  See above general comment/suggestion 55.  I always felt really unprepared for the projects, I did not know where to start with them because I just felt like we were not on that level yet. 56.  everything 57.  I thought that some of the projects far exceeded a class worth 2 credits. The hours put into the projects was somewhat extensive. 58.  It is boring sometimes. 59.  Very difficult for people who don't have a coding back ground 60.  The homework could have contained harder programming questions, but better tips/hints. 61.  The only thing wrong was the speed at which the TA's moved at times. I understand that this class has a lot of material and the TA's cannot go much slower but I feel like some of the topics needed extra time to be spent. 62.  Nothing 63.  The overhead could be a lot better 64.  Unless you go to the help sessions the projects are really hard to do and require lots of assistance from people who have already done it which doesn't help anyone learn. Give more instructions. 65.  Projects required to much time and using google rather than the website. 66.  Not enough instruction and practice to fully understand concepts. Also THIS IS NOT A 2 HOUR CLASS! I want more credit for all the work I did :/ I had no idea when I signed up for this little class that there would be so much work (especially projects). It was misleading. 67.  The class being taught by the TAs. 68.  The final project should also be structured and given a specific goal. 69.  Projects are exhausting. 70.  The lectures need to be more focused. 71.  Projects were pretty hard 72.  nothing 73.  Nothing, the class layout was fine. 74.  I definitely think this class needs a professor. 75.  The project descriptions and how to do them could be laid out better to make the objectives more clear. Also, the equipment we use in class could be upgraded. 76.  everything 77.  no 78.  Sometimes class time was not used to help with homework but towards the end it was well used to address problems 79.  Not knowing where to start at all on projects. 80.  Expected us to learn too much on our own!! 81.  Feel like I would have rather taken a intro to CAD class, rather than Matlab. 82.  The material did not look like it was useful for after this class. 83.  (See box below) 84.  Learning matlab wasn't good 85.  the time it took to do the projects was a lot more than expected 86.  I think that the lectures should be more interactive. I feel as if most of the time, the TAs just read from the lab and typed a code but we never really fully understood things. 87.  way too much work. I felt like I could turn in quality code if I had more time to analyze and go over my code, but I felt very pressured to turn in semi correct code in order to stay on track and keep a decent grade. 88.  everything 89.  Just not a fan of MATLAB. 90.  The multiple choice questions on the test were very tricky. 91.  The TAs did not care. We were not properly prepared for the projects or exams. 92.  Screen is too small so at last row of class was hard to see the screen and read. 93.  The TAs, the instructor, and the way they taught the class. It would be better to have more interaction with the students and ask them questions during the lecture. AND prepare for the lecture! 94.  It was kinda boring especially since I couldn't hear the TA's 95.  TA's think we are experts 96.  This class is much harder than I initially anticipated mainly because of how hard I found it to study for this class. I would consider creating some sort of generalized study guide. 97.  I spent a lot more time on it than I should have considering it is only listed as a two hour class 98.  the image session 99.  Some of the explanations for different commands were really just not helpful. And sometimes the in-class examples were missing explanations or weren't clear. 100.  I still do not feel confident in my ability to apply MATLAB outside of this class. 101.  The difficulty of the graded items was somewhat higher than that of in-class examples and often required online research outside of the class environment. 102.  the projects 103.  The material to learn is very hard, at times. more than one class period should be spent on the harder ones. 104.  Not enough taught on basic critical thinking on coding layout. 105.  I felt like not much programming was taught, just learning how to use MATLAB like a fancy calculator. 106.  The workload. The time required for this class is much larger than what should be for a 2 credit hour class. 107.  I don't know the coding languages very well at all so it was very hard to do some of the projects and class examples. 108.  The projects were way tooooo intense 109.  Curriculum was basic and some things seemed out of place or un-needed. 110.  I like the fact that if you do all the homework and work the examples then the code that you are able to get can help you achieve a good grade on the exams however the benefit from not having to do to much hard coding is minimal. 111.  fast pace and high level of difficulty meant it was easy to fall behind and very hard to catch up 112.  Several of the commands and functions asked about in the homeworks were not written in the lab for that day or talked about in class. This was frustrating when I felt like we were not learning about the material we were being questioned about. 113.  No one was willing to help when I had questions and the TAs made me feel 'dumb' whenever I would ask them for help 114.  It was really hard to find information on Matlab online. 115.  More involvement in the class from the students would have been beneficial. 116.  This class took up way more time than a 2 hour class should. Maybe just because I am not the best at Matlab, but some of the projects took up a great deal of time. 117.  The help sessions before a project or test was a nightmare to go to. They need to get a bigger computer room and more helpers. 118.  Matlab is a tricky, unforgiving thing to master. A lot like math. One mistake and you'll be debugging for at least 5 minutes. 119.  Some labs were not as clear as I would have liked. The website lacked some things taught in class and on tests 120.  i felt like some of the problems on the homework required knowledge that wasn't presented in the class or lecture. 121.  Not enough instructions on how to actually do projects. 122.  Sometimes the projects were hard. 123.  nothing really wrong. 124.  need more individual help 125.  The basics could have been explained a little more in depth for the people that didn't understand them at first. 126.  Projects were very very difficult. i had to find a lot of help to even get started on them let alone finish. 127.  The multiple choice questions on test can be a little ridiculous at times 128.  The lectures were not very helpful. Most of the time I ended up teaching myself during the homework. Perhaps working problems in class for participation credit would be useful? 129.  The projects are so long :( 130.  The third project (the image one). It does not really fit with the other projects/homeworks we were required to do, and was rather confusing. 131.  Some of the test required a lot more time then the class allowed 132.  Could have had slightly more creative projects (like final). 133.  If homework grades degraded after due date instead of immediately dropping letter grades I would have had a better grade. 134.  Projects were extremely trying. On the last exam, where the numeric parts had no partial credit, I missed entire problems for very minor errors. In particular I didn't type one character out of many lines of code and missed it. 135.  There was too much to know and it was taught too fast. 136.  For those who get the basics of programming and problem solving, some of the lessons moved a little slowly. 137.  This is a tough class to teach to everyone, especially students like me who aren't very good at coding. But I didn't see anything that needed changing. 138.  Seems as though it required a lot of time outside of class for only 2 hours of credit. 139.  The tests were very difficult. Many students that have to take this class will never use MatLab 140.  Sometimes, the examples did not make much sense when going back and looking at them, so it took a little time to understand it again. 141.  I did no think test are a good way to determine if someone learned matlab. I think projects show more how much you really learn. 142.  It was a little too fast for me and at times hard to follow. I might have benefited from more explanations/slower pace. 143.  Simply too much material was covered I felt like the class was rushed needed much more practice rather than just examples of problems need to teach material more thou roughly if possible 144.  We were often required to do some things that were not taught at all in class. I understand there should be a certain part of any class in which the student must try and learn parts for him/her self but it happened too often in this class. I do not blame this problem on the structure of the class as much as do the TA's teaching. I would have been much happier having professor Schleter teach my class. 145.  I thought that grading was weighted too hard on exams. I think that the projects should have been worth as much as or more than the exams, because in the work force, projects will be what we are concerned with. 146.  I did not like the way the project descriptions were presented. I had trouble figuring out where to begin on many of the projects. It took going to help sessions and learning from others. 147.  I have no idea how to study for the final. Maybe a final practice exam? Also, if there is to be a rework please make it for any test rather than just last one (I did very poor on second and very well on last because I worked my butt of...if I could rework the second, that would be beneficial) 148.  The student can get stuck on problems very easily outside of the classroom, where there is no one to help. A book might come in handy when a student has issues with understanding a problem or the examples on the website might be improved. 149.  Too much work for a two hour class! Moves a bit fast, and especially easy to get behind if you don't understand something. 150.  I am convinced that I haven't really learned anything that can be useful outside of matlab, and I still don't really see the use of matlab outside of this class :P 151.  October and November difficulty was a huge jump from first month content with no real climbing difficulty between. Easy one lecture, very complicated the next. 152.  e 153.  organization, TA helpfulness, no textbook, the labs 154.  grading was very nit picky. I put tons of comments in my codes and would get counted off for 'not enough comments' 155.  N/A 156.  The constrictive nature of everything that is done. 157.  Nothing 158.  The amount of credits given the amount of work. should be 3 instead of 2 credits 159.  The lack of using layman's terms left people inexperienced like me to spend hours trying to understand through searching the help documents. 160.  I feel like you should teach somebody how to do something so they can do it efficiently instead of making them learn it themselves proficiently 161.  Sometimes a lab web page wasn't structured clearly enough. Learning the material in class went well enough, but during review it was difficult to find all the information I needed. 162.  The projects. I thought we were supposed to be taught the material, not interrogate other classmates and TAs to find out what to do. This class would've been much more enjoyable if I knew what I was doing while coding besides waiting 40 minutes (literally, with my hand up) for a TA only to have him/her barely help. Seriously, one word to describe this class is disappointing. 163.  Projects required techniques not taught in the class. This could be overcome by going to a TA for help, but it might be more helpful if the material were posted as an additional lab. 164.  Could have been more active learning. 165.  There was so much that I was not familiar with and felt as if some of the projects were due too soon. 166.  I didn't think there were always enough examples done in class. 167.  The projects take too much time to complete for a 2 credit hour class. 168.  Projects were ridiculous. 169.  The help sessions were limited to late afternoon and a day or two before the projects were due. A lack of resources would be my opinion about what was wrong with the class. The message board is fine but the communication is somewhat limited when questions are asked concerning the projects. I also struggle with the multiple choice questions on the exams. 170.  I don't like the test set-up. I had the class at 8am, so I got the grade I earned. Yet, individuals in the later classes heard what was troubling on each exam and were able to figure it out beforehand. I don't like that set-up, because it puts some at an advantage over others. 171.  A little too difficult at times such as exam coding problems and projects. 172.  Getting up at 8:00 AM was rough! It would be great if there was more class time. 173.  Course content doesn't seem super useful. 174.  I did not see any issues. 175.  I don't think there were a lot of grades to help with the overall grade. Maybe there should have been more homework, more practice problems, old exam files, and more consistent grading. Maybe if the multiple choice was not such a large percentage of the scores it might have helped grades. Then again, maybe not. It would have been nice if all of the tests were formatted so you knew, if it was a fill in the blank question, whether you got the problem right or wrong. If you got the problem wrong and could not get it right then you should have gotten partial credit if you uploaded your code. Extra credit opportunities for all students would have been nice and alleviated some of the stress of grades. 176.  I didn't like how this class was taught solely by the TAs. I do like how they are there to answer questions, but when they are teaching the information, they are simply reading it off the website which I could do at home. 177.  The application of what we are learning is not always apparent or adequately explained. 178.  I already listed this at the beginning of this assessment. 179.  Projects are too time consuming 180.  Nothing 181.  Too much emphasis on topics that were meant to be "fun" (e.g. half of final project,entire first project, etc.), but were mandatory and devoid of fun. 182.  I have no real issues. 183.  A bit too much work for the credit hours. I agree that this much work is needed to understand the subject, but we should be getting three credits out of this, not two. 184.  Coding for me is a trial and error process, and I think that the testing format that requires coding in a certain (relatively short) amount of time is not a true test of understanding. 185.  My TAs weren't very effective with presenting the material. I think Prof. Schleter should have a bigger involvement in the teaching aspect of this course. 186.  As stated before, the expectations were a bit high for out of class work with only 2 credit hours. Maybe simpler projects or even just less time-consuming ones would help out this class a lot. 187.  Since I am not very proficient in computers, and I live off campus, I have struggled with finding help when I needed it. 188.  There was nothing really wrong with the class. The only main problem was having a single TA in the help sessions. It would sometimes take quite a while to have a question answered. 189.  It was far too demanding of you on projects. 190.  First off it is a 2 credit class that I spent WAAAYYYYY too much time on outside of class. The projects(minus the final) got progressively harder and took way to long to do. At one point i had approx. 20 hrs to labor in ONE project. And there is still regular HW and 4 exams plus the final. If you are going to keep that work load, then up the credits for the class. Rediculous for a two credit class. 191.  Make sure the test works as stated above. 192.  The website, inconsistently paced, the website 193.  I wish that either there is more time allotted in the class so that there is an opportunity to start the homework and ask questions in class. 194.  The tests seemed a little harder than I expected them to be, but other than that, the class was fine. 195.  It felt rushed to me, I think possibly covering less material in an equal amount of time would allow students to better understand the basics. 196.  Other than my comment above about the amount of time spent outside the class on homework, nothing. 197.  the projects are not related to the materials we are taking 198.  It was alittle very challenging at times 199.  The second half of the semester is much more complicated then the first half...which is understandable, but I think this class being 2 days a week (TR) is a problem, the second half of the course would be better if it could be broken up over more time and the fact that it is 2 credit hours is also unfair! This class requires the amount of work that a 3 credit hour course would expect! I think it should be a MWF class that is 3 credit hours in all honesty. I think that it would make the course way easier to understand and follow. The way the class is now, you cover a subject over one day and barely come back to the topic other than for homework or if happens to be on a project and/or test. If the class was broken up over time there could be two lectures on the same material and it would probably stick better with students! 200.  matlab was never interesting 201.  N/A 202.  I spent more time on this class than most of my 3 and 4 hour classes. I wish there was not a project due during finals week when I need to be studying for other tests. However, I do realize that it was assigned well before the due date. 203.  I liked the format for the third test, not the first two. Its very helpful to know if you got the answers right so that you can manage your time well. 204.  projects are more in depth then anything covered in class. requires alot more knowledge then is really taught in class 205.  I obviously don't know much about this because I haven't been in the workforce yet, but I kind of wonder how some of the stuff we covered will be useful to me in the future. 206.  Matlab is the worst 207.  Some of the projects required a little too much information that we didn't cover. 208.  Some of the projects required extensive research beyond what was taught in class to complete the project completely. 209.  I feel like some of the topics were irrelevant and were just filler busy work. Better understanding of the major concepts would be more relevant in my opinion. The class could've been taught better as well. 210.  The back-end, as I have stated, tended to get muddled and bogged down in the considerable coding. I felt a refresher or a more gradual approach would have been more able to present the material. As it is, I am still unsure about minor, but key, aspects.

Make at least one constructive suggestion on how this class might be improved. 'Free food' or 'Cancel the class' are not constructive.

1.  more sleep time 2.  Try to not cover as much material at once. 3.  tas should be a little more prepared so that they can explain a little faster and then give more examples which aren't all about the same and not really like the homework 4.  Maybe scale the projects differently or exams. I just feel like I put in a lot work to this class 5.  Have the TA's go a little bit more in depth about each example, explaining a little bit more on each command or subject. 6.  idk..... maybe a prelab to do to get you familiar with the material before you learn it. 7.  none 8.  Make lab pages a little longer and cover more material, even if it isn't presented having all of the information we require in one place would be helpful. 9.  teach more hopefully stuff in class 10.  More example walk-throughs, and short, in-class problems that could be checked and graded by an online system. A higher level of excitement. 11.  If you insist on having projects make them shorter, easier, or less of them - also weight them evenly. Quit grading projects so harshly - so what if you don't have 400 comments, if you knew what you were doing and your code works you should make an A on the project, which isn't the case currently. It's like the graders are desperate to find reasons to take points away. This class feels like you're set up to struggle instead of setting you up to succeed. 12.  I think adding another project because those are from what I learned best 13.  can't really think of anything 14.  Even if it is keeping the same format of the class-only make sections available for certain types of engineering majors. While having computer science TA's teach us is great-it would be nice to see if we would actually be using this in our careers. 15.  The lab lectures are hard to follow. Simplify explanations. Prepare more for the lectures beforehand. Make the projector brighter, and make the display larger. Don't ask us to answer questions and complete projects unless all the necessary information is clearly covered in the website. 16.  Have more TA's or some assistant in help sessions so that students can get a more timely response and not waist so much time. (I do understand however that there are hundreds of students in this class however) 17.  Don't have a 3rd exam on last 4 lectures. 18.  Remove the attendance grade and allow students to be responsible for their own learning. Don't punish students for being able to learn independently. 19.  Better coverage of fmincon Make extracting images from the EF website more intuitive - I couldn't access them before exam 3 because I didn't know to add a .png to the end of the website name If you are going to give example problems before an exam (not the practice exam, the practice problems) please provide the solution codes, at least before the exam begins. It's frustrating to have no clue how to begin something because the code in the lab overly confused you. 20.  Like I said earlier, I think the homework should always include a coding section for the students to learn better. It is easy to just click through multiple choice after getting frustrated. 21.  Make the labs more engaging and start simple then work to complicated with different ways of doing code 22.  while everyone is coding and no one is lecturing, music. 23.  See above answer. 24.  More simple examples to lead into more complex ones. I often felt lost at first as some of the jumps in difficulty felt to large. 25.  I would make the homework grades a smaller percentage of the grade 26.  Slowed down and explain a little more in-depth. I do more work in here than in my 4 credit hour class so need more credit hours. 27.  More office hours. Having only two days for office hours is difficult. 28.  I would like a little more variety in the class. The final project is the first chance we've gotten to do something fun with matlab. I would have had more interest in the class if there was a greater chance for creativity throughout the class. 29.  Earlier notice on projects would be nice. I always started right away and worked steadily, but still felt rushed toward the end. 30.  Actually explain the information. The information in the labs were a lot easier than what was expected from us. 31.  A book and more coding interaction that allows us to understand what is going on because it is not always clear. 32.  Add more info to the website 33.  Free food, cancel class is good. Also have one more person in the lab for project help sessions. 34.  Allow reworks for all tests and provide practice exams more like the actual tests. 35.  more emphasis on the last few labs, I felt they got sort of rushed or I just had a lot to do in other classes, but either way I didn't fully understand that entire section as well as the first two 36.  It would be good if there was more time to ask questions at the end of class. 37.  Make our projects have a focus in terms of a variety of topics, but less strict guidelines about what we must do. Essentially, provide aspects that should be included and then allow us to design something ourselves. 38.  Make an A a 90 like (almost) every other class. Other than that, it's a pretty solid class. Other people seem to have trouble but I never have. Maybe a bit more emphasis on how you have to tell a computer to do things - that seems to throw people through a loop. 39.  na 40.  take some majors out of the requirement of taking it 41.  Similarly to what I thought was wrong with the class, I think having more short answer problems would be beneficial to our understanding of how matlab works. 42.  Like I said before I think the class should be a 3 credit hour class. People talk about Statics being a hard 2 hour class but it doesn't compare to this class in my eyes. 43.  Put more SIMPLE example problems in the lab that are similar to the hw and test questions. Too often I needed to teach myself how to use some sort of command or function and I would go to the example and it would be a 3 page long code that used random functions that I had never seen before in my life that could only be understood by Dr. Schleter. Put more examples in there that we can follow and teach ourselves some of the material because when a class is only taught by TAs a lot of material is either missed or poorly presented and it is left for the students to teach themselves. 44.  Homework is too frequent, I'd rather homework of huge amount at the end of each module or semester. 45.  Maybe finding helpful videos on youtube or something that will be a little more helpful for learning on your own time 46.  I really do believe that if a textbook was required and followed. A textbook that has problems and solutions. This could be really help students. And the exams should test students on similar hw problems. This help/rewards students would put in the effort to understand the hw. 47.  make TA's learn a little bit more about MATLAB 48.  Slow down the class if possible. 49.  More help sessions, better hints or easier questions for the coding problems and more detailed explanations on how to do the coding for each section both in class and on the website. 50.  For one of the projects a video was uploaded to the website that further explained how to tackle a particular step in the solution of the problem. I found this video to be extremely helpful. It clarified what needed to be done to be successful in completing the project and it was simply another presentation of the material. Sometimes the material in class would be covered to quickly that supplemental instruction would have been very useful in further understanding a particular topic. These online videos would be great study tools. 51.  More TA's 52.  Bigger screen in the lecture and a mic or something for the TA's 53.  I really did not like the layout of the first two tests. Even when I would spend a few hours studying for the exams, there was always a small error that completely ruined my grade and I just didn't think it was an effective way of demonstrating our knowledge of Matlab. 54.  See above general comment/suggestion 55.  I sometimes felt like the TA's were unprepared for the lab of the day, almost like they were reteaching themselves at the same time. I think they should be required to go through the labs before teaching them. 56.  dont just give code and go through it with the class this doesnt help we should write the code together as a class 57.  I think there were too many projects. Another one would be posted before the grades from the last one were even released. 58.  Make it an online class! 59.  Go slower 60.  If the class could increase to a 3 hour credit, a small recitation that met once a week would be helpful. 61.  Move a little slower through the examples and the TA's should project their voices more. 62.  Great class as is 63.  Keep the new good overhead with bright screens instead of the dull dark one. 64.  Go slower, talk louder, make the code larger on the screen so everyone can see. 65.  No attendance grades. 66.  Give extra credit opportunities. 67.  Don't let the class be taught by TAs. 68.  More one on one time seems like it is needed. 69.  Make projects lighter, and dont pile so much on towards the end. 70.  This class could be improved by better explanations of the example programs. 71.  turn more class days into project work days. I couldn't make many of the help sessions 72.  more help sessions 73.  As stated above, the only change I would make to the class is the type of examples worked. 74.  If the professor was more involved, I think all of the students would be more knowledgeable and learn more about matlab. 75.  Improve the equipment used in the class (projectors, computers, etc.) 76.  less projects 77.  more example 78.  Have EF 105 and 230 in back to back semesters so students still have some knowledge of how MATLAB works 79.  Projects could be broken up more. 80.  More practice problems on the homework!! More practice problems for the test! 81.  Don't use Matlab in the future. Use something useful like intro to CAD. 82.  They should have related the materials to other classes that we would use Matlab. 83.  Adding more coding to the homework like the last few homeworks would help. I feel that there was too much multiple choice in the earier homeworks, so I wasn't as comfortable with actually using important topics such a functions, subfunctions, and loops until halfway through the class. 84.  Consider making this class online with more online help and videos and have class once a month to keep everyone on track and answer any questions but also have help available at the computer lab. 85.  Have more descriptive examples for all the topics/problems in class. 86.  Balance the workload with the credit hours 87.  Again, set up more developed projects that require more developed thinking over a certain problem. Three tests, four projects, a final, and homework every week is a lot of work when you are just starting out to code. 88.  too many to list 89.  Maybe a page of helpful links. I spent a lot of time Googleing the material outside of class. 90.  Have the homework be worth fewer points. It is a good way to learn the material but it is frustrating to work through the homework and kill your grade at the same time. 91.  Get TAs who care and have help sessions. 92.  Bigger screen in class 93.  TAs should prepare for the lecture before the class. 94.  Make the labs more interactive, it seemed like I just sat their most days. 95.  TA's should take it slow and not assume that we are all experts 96.  I would attempt to make the practice exam problems more relevant to the actual exams, therefor rewarding the students who take the time to complete the practice problems. 97.  Maybe more smaller projects instead of all reletively large projects 98.  only go over one concept each lab. most everyone I talked to never understood the lab after class was over 99.  More details about complicated command, etc. The information on fmincon was really bad and I still don't understand it. 100.  Many of my friends have been able to use MATLAB as a way to complete their homework. Although I have a generally understanding of MATLAB, I'm still not sure I feel like MATLAB would be the best use of my time when trying to complete my homework correctly and efficiently. Incorporating more real time applications and possibly allowing students to work on homework for another class, say physics or dynamics, and having the TAs present to assist in writing the program, etc. would add to the takeaway from this class. 101.  A book for the class that goes into more depth than in-class time can. This would make it possible for students to study more difficult coding problems more effectively. 102.  explain the projects more and provide more direction 103.  More interactive examples, possibly. 104.  Give more feedback on project code. 105.  HW could be more practice coding. It was easy to do the HW without knowing it really. 106.  Screen the TAs better. 107.  Utilize the class time better. 108.  Make the lessons more related to project stuff. 109.  More 'major' applicable coding topics. 110.  I think the numerical approach to the exams is much better than the hard coding only because of the time crunch and maybe a little less emphasis on the multiple choice questions which can be ambiguous occasionally. 111.  Break it into two one semester classes to make it easier to keep up 112.  spend less time on the nonessential stuff - the extra message boxes and image analysis - and more time on real engineering problems that can be solved with Matlab 113.  Be more approachable 114.  Have a source of more organized Matlab information. Perhaps a recommended textbook would be good. 115.  Having one free participation grade would have been nice. 116.  Make it less time consuming. 117.  I think they need a bigger computer lab and i also think more examples of code would help. I think the examples on the website should be updated and it should be more useful to this semester of classes then to past semesters of classes. 118.  Free food would be great but engaging the students in class discussion is more productive. 119.  Optional Reminders about HW or project due dates could be sent to eliminate missing assigned work 120.  i would really like to see some type of textbook or resource packet for students to refer to during and after they take this class. 121.  Should cover more instructions of project in class. More TAs(grads and undergrads) during help sessions. 122.  I say it could be better if the examples were more complex. 123.  After projects are due, show a full example of how it could have been accomplished. 124.  small help sessions for more individual guidance. 125.  More simple examples before the advanced examples for better comprehension. 126.  Make projects simpler, offer more help on getting started. 127.  If it is a multiple choice question it must be somewhere on the website...right? 128.  In class problems that are required. Keeps people from having glossy eyes. 129.  More work with simulink. 130.  Replace the third project (the image one) with a project that better showcases features of MatLab that we are actually more likely to use. 131.  Better hints on a homework questions. 132.  Have extra "labs" that students can read if they would like to know and understand matlab even more. 133.  I think that following along in class by doing it yourself is a good way to learn. 134.  On the last exam, where the numeric parts had no partial credit, I missed entire problems for very minor errors. In particular I didn't type one character out of many lines of code and missed it. I suggest always planning tests to have options for partial credit. That would be awesome. 135.  Teach more relevant material for a basic knowledge and make sure that the understanding in key areas was good and solid. 136.  Short coding quiz at the beginning of class over the material to be covered for that day, if a student gets it correct, they are not required to attend the rest of the class. 137.  The class was overall pretty great. I think more TA's at the day-long project help sessions would be lovely. 138.  Maybe a few more hints on homework problems that were not covered in class. 139.  Make the tests easier and like the homeworks. It is very hard to right multiple functions during the time period we are given 140.  Make it more interactive with the students figuring out the correct way to code. 141.  I think this class may need more TA to help the students who struggle with matlab 142.  More interactive--make sure everyone has a chance to get caught up before moving on with class. 143.  Needs to be more organized and projects be explained clearly before assigning them 144.  I understand it would not be feasible to have professor Schleter teach every EF 230 class but to have him in at least a couple classes a semester of every section could be nice. 145.  To me, it seemed that the exams were too heavily weighted on the multiple choice. Also, as previously stated, I think that the projects deserved more weight than the exams, because in the real world, projects will be what we will be concerned with. 146.  I think online step by step solutions to coding questions on tests would be beneficial. 147.  I would really dumb down the concepts in class for the subjects..really nail their meaning and uses, then make the homework questions more challenging 148.  Improve the website examples so that when a a student gets stuck outside of class they can go back a figure the problem out from online. 149.  Maybe add more helpful content in the later labs. The functions get more complicated, but the website material became more vague. It was often hard to go back and find how to do little details in the functions. 150.  I consistently felt a little too rushed on the exams, and felt they were a little too long for the time constraints. I acknowledge that I am a slow worker, and I am sure this wasn't a problem for a lot of people, but I never really felt like my knowledge was effectively applied on the tests because I felt rushed. That is a very minor suggestion though. 151.  More examples with the more complicated material(ode45, differentiation, integrals) 152.  e 153.  get textbooks or some other way to get outside help for people who can't be on campus all day 154.  Better explainations of code commands 155.  N/A 156.  Be more lenient with the grading. If a program works, it WORKS. 157.  Slow down and give better examples of certain topics. 158.  Have an total extra credit opportunity that can boost your overall grade by 5%. Meaning you can have multiple opportunities for like 1% overall each or have like an extra project game that is worth all 5% of the extra credit. 159.  Having a way to make sure students are following in class, like clicker questions, would help keep us attentive. 160.  Teach slower 161.  It would be helpful if the labs were outlined a bit more concisely for the sake of reviewing the material. 162.  Have Prof. Schleter teach some of the sections sometimes, not just one section. I think you'll notice section T5 has consistently higher averages than the other sections on everything. Schleter just so happens to teach this section. Coincidence? I doubt it. Maybe the matlab professor should visit the other sections and let us in on the actual learning. I've said it before, it is demoralizing to have one section's average literally 10 points higher just because we got screwed over. 163.  Create additional optional labs to explain project material, or remove labs that were not as useful(such as the sound lab) to provide this information. 164.  Emphasize pseudocode more so thinking like a programmer can be better understood. 165.  I would feel that breaking the class up into two 1 hour classes for both semesters would help. 166.  I would make more in class grades so that students are "forced" to pay attention. I think this would help learn the material as well. 167.  Extra help sessions, particularly around project due dates, would be nice. 168.  More examples. 169.  The projects were overwhelming, especially the second and third projects. The help sessions, scheduled before the projects were due, were always so crowded it was difficult to get help. I would recommend extended help sessions the week before the exams and before the projects are due. I would also recommend some optional programming questions to prepare us for the tricky parts of the projects(i.e. the scale conversion portion for the third project. 170.  Different tests for each section with similar topics. Make lecture more interactive instead of just a TA going over the material really quickly. 171.  I think a textbook on Matlab would help a lot especially for the people who don't excel in programming. 172.  I think that making the coding section on exams multiple choice was a good idea. I think that the exams should always be that way. 173.  Teach things other than just MATLAB. Like maybe coding in python, how to write stuff in Mathmatica, html, how to make graphs in Origin, data mining, etc. I don't know how to do any of these things and wish at least a few things other than MATLAB were taught. 174.  It would help if the in class examples had more explanation within the code, so more annotation. 175.  There are so few TAs per class that there needs to be a system on every computer that if you need help, you press a button and your name automatically enters a queue. Then you don't have to continually raise you hand for help, the TAs can serve on a first-come, first-serve basis, and you can continue to work on your code or homework while you wait. Also, I feel like there should be more extra credit opportunities and more consistent grading of assignments, and that all projects should be due about a week before the tests to force students to study. Overall, I thought the course was very interesting and very beneficial to me! Now I don't cringe at the sound of Mat-Lab ! 176.  I wish we would have had a little exposure to Simulink. Maybe one or two labs that gave us an introduction to the software. 177.  Be more specific when answering questions, especially when the questions are related to projects. 178.  Make all homeworks due on a certain day (ie: every other Wednesday or something along those lines). One less project. 179.  Simplified projects 180.  Maybe video for explanation 181.  Focus less on open-ended coding projects. The projects themselves (save the pi approximation) are unrealistic and a senseless waste of time when the same topics can be practiced in-class and tested on with an exam question. 182.  I honestly thought everything was fine with the class. Some of the project descriptions and homeworks were a little unclear, so maybe work a little with that. 183.  Like I said, one more credit would be really nice for the workload, and then that would put another class period in as well probably which would help as well. 184.  More weight on projects (especially useful ones like the year end project) would be appreciated. I know that one has to establish the basics of a class and test understanding some way, but if grades were linked to projects that served to help the student outside of class, there would be a more accurate snapshot of student understanding. I, for one, have learned much more about matlab when working on the projects than I ever have from homework and tests. 185.  Prof. Schleter should be more involved in actually instructing the course. He would undoubtedly present the material much more effectively than a group of TAs that don't act like they really want to be teaching it in the first place. Also, there should be a required textbook and optional reading assignments for extra supplement of the material covered. 186.  Have more time at the end of class to work on homework and ask questions about assignments. Also, maybe the possibility of group projects? It would cut down on the work load for each individual student and it would also cut down on the number of items to be graded. It's a win-win for everyone. 187.  More instruction on indexing and more hours for extra help. 188.  Maybe a recitation class or session to review topics if they weren't understood in class... 189.  Teach us, at least at some point, the commands that are used on tests. I found that a lot of things didn't come up until test day 190.  If you do not get functions and loops then you are pretty much screwed. Spend more than one class on funtions and loops if that is CRITICAL for the success in the remainder of the course. 191.  Make this class a three hour class. I spend the same amount of in-class time as any other 3 hour class, and more out-of-class time than most 3-hour courses. 192.  Make some updates or adjustments to the website. Though this may just be due to lack of accommodation with the website, I found myself having to open a handful of tabs just to work throughout the website. Other than the website and the lengthy projects, the class was very enjoyable. 193.  More time. 194.  Giving the answers or hints to the practice exam problems would be helpful. Though it is difficult if the problems on the exam are similar or almost identical, it lets people who are trying to study not get frustrated and give up and then feel terrible when the exact same problem is on the exam and they don't know how to do it. 195.  Group work! I often criticize group work, but, for me, this material was very difficult and it usually helped to meet with someone to go over it. I think maybe groups of 3 or 4 would be great for projects while still having individual tests to ensure that each student is understanding the material. 196.  A textbook recomendation. 197.  id say, this class should focus on only homeworks and projects. idont think exams are useful for this class. ill suggest it become 65% projects and 35% HW. 198.  Give more time during class for project work so the TAs can answer more questions. 199.  I think the class should be 3 credit hours because it requires the amount of time in class (150 minutes per week) and outside of class with homework twice a week and 4 major projects. The fact that the class is only 2 hours does not seem fair! If the class were upped to 3 credits it would make more sense. I have talked about this issue with many students in the class and who have already taken it and they have all agreed with me on that. I personally think if you guys made the class 3 hours then it could also become a MWF class instead of TR and that would be the best improvement in the course! Spreading out the material would stick better in our minds. The second half of the class was more difficult to understand and properly implement, but could be made much easier if this class were switched to MWF! 200.  if there were more examples of practical applications 201.  Interact more with the class. 202.  fix the clarity/visibility of the projector 203.  put the notes from class on the website. Those notes are often the most helpful in solving homeworks and it's tough to type the notes exactly during class because of the speed of the lectures. 204.  make the projects more like what is taught in class and less intense. 205.  I wouldn't worry about doing as many projects. Maybe get rid of one project or make all of them a little shorter/simpler. 206.  Make all of the projects due in different parts, similar to the last project we had. 207.  There was practically no engagement between the TA's and the students during class. This is mainly the students fault but i feel like if there was a little more interaction the class might flow more smoothly. 208.  Include more info on Simulink 209.  Relate the projects to the material more and get more in depth on the important concepts. 210.  The exams should follow the same guidelines as the third. Our time block just is not enough to finish the ranging multiple choice and then dive into more than moderate coding. The first exam toed the line, with the commenting deductions being a pain. Short answer is fair, I think.